Provide more structured data in SyntaxError

[bartlomieju]

I already opened #56 to have more granular control over how error messages are displayed.

It would be lovely if SyntaxError could provide additional information like "start" and "end" position (a "range") of the error (if that's possible) so that users of the crate could crate more rich error displays, something like dprint-plugin-typescript does:

Error formatting: /Users/ib/dev/deno/broken.ts
   Expected '{', got 'interface' at file:///Users/ib/dev/deno/broken.ts:1:8

  export interface Foo }{}
         ~~~~~~~~~
Checked 1 file

In this particular case we have a range that points to the "interface" keyword which is underlined.

[g-plane]

Source code is parsed directly without tokenizing/lexing, so it doesn't know where the end position is.

[bartlomieju]

Makes sense, I can just point to the concrete line/column without a range then :) any chance you could cut another release so I could leverage #56 and #58?

[g-plane]

https://github.com/g-plane/markup_fmt/releases/tag/v0.13.1