Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors not showing up until I open file where error occurs #169

Open
marcinjahn opened this issue Jun 25, 2024 · 1 comment
Open

Errors not showing up until I open file where error occurs #169

marcinjahn opened this issue Jun 25, 2024 · 1 comment

Comments

@marcinjahn
Copy link

marcinjahn commented Jun 25, 2024

I noticed that csharp-ls will not show me errors in my repository until I open the files with issues manually.
E.g., if I change the name of some class (without using LSP rename feature), and that class is being instantiated in other files, I will not get any errors until I start opening each one of these other files.

Is it an expected behavior? In solutions with tens of projects, it's quite inconvenient.

I'm using csharp-ls with Neovim and the https://github.com/Decodetalkers/csharpls-extended-lsp.nvim.

@razzmatazz
Copy link
Owner

Can confirm I can see this on VS Code, at the very least.
The issue is that csharp-ls does not implement the "workspace/diagnostic" LSP request and thus client is left to its own devices to accumulate diagnostics from the server as it sends them only for files that have been open recently.

TODO: implement https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_diagnostic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants