> But this seems to be a VSCode issue. That’s a protocol issue! While LSP has a method to report a transient (edge triggered) error, it doesn’t have a way to r

> But this seems to be a VSCode issue. That’s a protocol issue! While LSP has a method to report a transient (edge triggered) error, it doesn’t have a way to report a persistent (level triggered) status. And to solve configuration problem, you really want a “status” concept - you need an LSP health indicator which is either red or green, and which you can click on to get info about what the server thinks the project is. There’s no such feature in LSP at the moment. https://github.com/microsoft/language-server-protocol/issues/511#issuecomment-652549272 https://github.com/microsoft/language-server-protocol/issues...