You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I start the language server, it runs the validation, and adds a bunch of warnings/errors on my source files (all great)
I close all the editors, the errors and warnings stay around (makes sense)
The language server is shutdown being the scenes, the errors and warnings stay around (makes sense, too)
I open the preferences and switch the errors/warnings off because I want to get rid of them - BUT THIS DOESN'T REMOVE OR CHANGE THE EXISTING ERRORS/WARNINGS. They stay around.
The reason for this is obvious (the language server is not running to take the new preferences into account and update the errors/warnings). When I startup the language server, it reconciles everything and the errors/warnings are gone (for my case described above).
But it might probably not make a lot of sense to the user that the errors/warnings wait for the language server to kick-in before they get removed (due to my changed preferences).
The text was updated successfully, but these errors were encountered:
If we keep the language server around even if no editor is open, that would solve this (as a side effect), but I am still not fully convinced that we should keep the language server running all the time.
Another solution would be to start a language server if the preferences for validations get changed and no language server is running, so that those changes can take effect (under the hood).
Validation are removed if LS is shutting down with 35f4e98
Therefore, this concern should be addressed. If LS is down there won't be any validations from LS left on the client
I am looking at the following case:
The reason for this is obvious (the language server is not running to take the new preferences into account and update the errors/warnings). When I startup the language server, it reconciles everything and the errors/warnings are gone (for my case described above).
But it might probably not make a lot of sense to the user that the errors/warnings wait for the language server to kick-in before they get removed (due to my changed preferences).
The text was updated successfully, but these errors were encountered: