The documentation says:
> Difftastic output is intended for human consumption
Why not separate the human-consumption part and the underlying parsing part? Or at least provide both in the same utility?
> Difftastic output is intended for human consumption
Why not separate the human-consumption part and the underlying parsing part? Or at least provide both in the same utility?
Difftastic then converts the tree-sitter parse tree to a simpler s-expression style format (see https://difftastic.wilfred.me.uk/parsing.html#simplified-syn...), and computes differences on that.
I'm just trying to clarify that I'm not generating conventional 'unified diff' patches, so I can provide a nicer interface (e.g. line numbers).