Open OliverJAsh opened 8 months ago
We had notifications in the past and move to language status since notifications are annoying if you open workspaces where you can't fix this. So if we bring notifications back it has to go behind a setting.
We had notifications in the past and move to language status since notifications are annoying if you open workspaces where you can't fix this. So if we bring notifications back it has to go behind a setting.
In terms of notifying, I find the way prettier
does it more than suffices to draw the person's attention to the fact there is an issue, which can then be debugged in output.
VS Code's recommendation for something like this is to use a language status.
If every extension has its own status indicator this will look very crowded.
The user can select which indicators they wish to see? I would also consider eslint - along with prettier - to be perhaps the 2 most import for a developer to be able to monitor while working.
Also a split between soft errors (current file not included) and hard errors (eslint crashing/failing to configure) would very helpful.
Yes, the user can ping the ESLint indicator to the status line.
The status of ESLint is indicated in the status bar by the tiny
x
symbol:This is very difficult to spot. I want to be alerted as soon as there's an issue. Could we send a notification when ESLint fails to load?
For context, I encounter these errors quite frequently because my ESLint config depends on custom rules that need to be built prior to ESLint running. A notification would serve as a useful reminder that I need to build my custom lint rules.