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

[LSP] Report syntax diagnostics from document pull without waiting for semantic diagnostics #62560

Closed
dibarbet opened this issue Jul 12, 2022 · 4 comments
Assignees
Labels
Area-IDE LSP issues related to the roslyn language server protocol implementation
Milestone

Comments

@dibarbet
Copy link
Member

Reported by @CyrusNajmabadi

Currently there is some perceived slowness in diagnostics because we always compute syntactic and semantic diagnostics before reporting anything to the client in document pull. It can take a bit to compute semantic diagnostics which is expected. However, we can generally compute syntax diagnostics fairly quickly and in the old system we would push those first so that they show up fast.

Document pull supports streaming, so we should compute the syntax diagnostics first, send a report, while we are still waiting for semantic diagnostics to be computed.

@dibarbet dibarbet added Area-IDE LSP issues related to the roslyn language server protocol implementation labels Jul 12, 2022
@dibarbet dibarbet self-assigned this Jul 12, 2022
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Jul 12, 2022
@gundermanc
Copy link
Member

FWIW Visual Studio's LSP client supports progressive notifications in document diagnostics but it doesn't actually update the UI until all of the notifications have landed.

@dibarbet
Copy link
Member Author

FWIW Visual Studio's LSP client supports progressive notifications in document diagnostics but it doesn't actually update the UI until all of the notifications have landed.

Thanks for catching it before I tried and failed. Filed https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1569172

@CyrusNajmabadi
Copy link
Member

@dibarbet can this be closed? we do have different providers now for syntax/semantics right?

@dibarbet
Copy link
Member Author

yup, closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE LSP issues related to the roslyn language server protocol implementation
Projects
None yet
Development

No branches or pull requests

5 participants