Maurice Nicholson 981ef6f821 Better source line and column numbers (#2213) ... Attempt to improve the graphical reporter source file **line number** and **column number** . Currently `oxlint` renders the **line number** as the first line in the snippet **column number** is always `1` AFAICT. Example of current version on VS Code repo:  This means that when CTRL-clicking on the source-file:line:col "link" it takes me to the wrong place. This PR is an attempt to improve things by getting closer to the source of the issue. Here is my version again on VS Code:  I'm a bit worried that none of the tests failed though - would that be expected? Also the approach feels naïve and there may be several cases it won't work for, or won't work quite so well. Specifically it's just finding the first labelled-span, but I'm guessing in some cases that could be providing context, rather than the thing the user would want to change. As before I'm no expert and any feedback is very much appreciated. Also in my local testing, VS Code is still a bit unpredictable - even with the correct line + col it will always go to the correct line number but doesn't always go to the correct column 🤷 But that's not our issue 😄		2024-01-30 12:26:16 +08:00
..
src	Better source line and column numbers (#2213)	2024-01-30 12:26:16 +08:00
Cargo.toml	refactor: move all miette usages to oxc_diagnostics	2024-01-28 16:52:16 +08:00