Log the span of code concerned by an error message, not just its line

[ClementSparrow]

And clicking on the error message should select the code?

[david-pfx]

From a parser point of view that sounds pretty hard. Do you have a repro case?

[ClementSparrow]

It's not only getting the position of the error in the line that is hard, it's also changing the error reporting system to show the part of the line, and be sure the unit tests are not broken by the change (they tend to break when the error messages change).

[david-pfx]

I misunderstood. You want to highlight the columns within the line, which effectively is just the current token. Should be easy enough.

My preference in testing error messages is test for contains rather than is exactly equal to. As long as there is an error with roughly the right text, any deviations are probably tolerable. If not, maybe regex is the way to go but preferably not.