Diagnostics in the IDE

[aminya]

dprint prints the errors that it encounters in the output channel of the IDE. However, it doesn't create diagnostics. It would be great if it does.

Instead of this, we can have a proper diagnostic

[dsherret]

Aren't these kind of diagnostics usually already reported by most IDEs? I'm not sure there would be much value in this because of that and it might get confusing/annoying to get diagnostics from dprint and other sources about the same thing.

[aminya]

It could be configurable so that the user can decide. In my case, I wanted to replace the Eslint plugin with dprint and use Eslint through Dprint. Having diagnostics is the missing part.

[dsherret]

Do you have an example of dprint providing a diagnostic, but your editor doesn't? Most people have language servers installed for the language they're using or they get diagnostics that dprint would report OOTB.

I'm still not sure this is worth the effort. It would be a decent amount of work. Additionally, currently the plugins only return the first diagnostic they encounter rather than all diagnostics for the file. To change plugins to be able to return multiple diagnostics would be further work for both dprint's CLI and for the plugins. Then it reporting all the diagnostics might be too noisy for some users so that would need to be configurable, so probably it should just keep reporting the first one.