Coming soon: line numbers for a bunch of errors & warnings

One annoying QoL issue we've had specifically with compile time errors is that often Ash would tell you that something was wrong, and even what module, section, option path to look in, but it couldn't say exactly what file and line to look at. Thanks to some great work from @Jonatan Männchen, we now have that capability 🥳 I've done the work to integrate that amongst a bunch of our compile time errors & warnings, and it gets us in-editor warnings finally.
No description
5 Replies
nikfp
nikfp2w ago
Does this surface directly through the LSP, through the Spark extension, or through another mechanism? ('cause this is awesome!)
ZachDaniel
ZachDanielOP2w ago
directly through the LSP just using diagnostics
nikfp
nikfp2w ago
That's great, yet more awesome work from the Ash team. Now just waiting for the Expert team to catch up with Spark extensions so the rest of the niceties work....
Sienhopist
Sienhopist2w ago
And better static analysis from the compiler in general 🙏
Shahryar
Shahryar2w ago
it works on Zed?

Did you find this page helpful?