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

Add support for reporting non-local LSP pull document diagnostics for open documents #69541

Merged
merged 3 commits into from
Aug 20, 2023

Conversation

mavasani
Copy link
Contributor

@mavasani mavasani commented Aug 16, 2023

Fixes #5634

Implemented as per dotnet/vscode-csharp#5634 (comment) - thanks @dibarbet, your suggestion works like a charm!

Currently, we only report local document diagnostics for open documents in DocumentPullDiagnosticHandler. We report local and non-local diagnostics for closed documents, as well as no-location project diagnostics in WorkspacePullDiagnosticHandler.

This change adds a new dynamically registered document diagnostic source in the public DocumentPullDiagnosticHandler with a new identifier to report non-local document diagnostics for open documents. I verified that after this change compilation end diagnostics are reported for open documents when FSA is enabled.

… open documents.

Fixes dotnet#5634

Implemented as per dotnet/vscode-csharp#5634 (comment)

Currently, we only report local document diagnostics for open documents in the DocumentPullDiagnosticHandler. We report local and non-local diagnostics for closed documents, as well as no-location projects in the WorkspacePullDiagnosticHandler.

This change adds a new dynamically registered document diagnostic source in the public DocumentPullDiagnosticHandler with a new identifier to report non-local document diagnostics for open documents. I verified that after this change compilation end diagnostics are reported for open documents when FSA is enabled.
@mavasani mavasani requested a review from dibarbet August 16, 2023 15:00
@mavasani mavasani requested a review from a team as a code owner August 16, 2023 15:00
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Aug 16, 2023
Copy link
Member

@dibarbet dibarbet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great to hear that it worked! A few comments, nothing major I don't think

Copy link
Member

@dibarbet dibarbet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

apologies, this slipped my mind. lgtm!

@mavasani mavasani merged commit 1642dbc into dotnet:main Aug 20, 2023
24 checks passed
@mavasani mavasani deleted the LspCompilationEnd branch August 20, 2023 14:57
@ghost ghost added this to the Next milestone Aug 20, 2023
@dibarbet dibarbet modified the milestones: Next, 17.8 P2 Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants