Skip to content

Initial draft of LSP pull diagnostics for documents.#47914

Merged
66 commits merged intodotnet:master-vs-depsfrom
CyrusNajmabadi:lspDiagnostics
Oct 1, 2020
Merged

Initial draft of LSP pull diagnostics for documents.#47914
66 commits merged intodotnet:master-vs-depsfrom
CyrusNajmabadi:lspDiagnostics

Conversation

@CyrusNajmabadi
Copy link
Contributor

No description provided.

@davidwengier
Copy link
Member

You also need to add a method to this nonsense here: https://github.com/dotnet/roslyn/blob/master/src/VisualStudio/Core/Def/Implementation/LanguageClient/InProcLanguageServer.cs#L142

And you probably need to update the Initialize handler to tell the client that we support pull diagnostics, here: https://github.com/dotnet/roslyn/blob/master/src/Features/LanguageServer/Protocol/Handler/Initialize/InitializeHandler.cs#L43

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.

I'm a little unsure of how the diagnostic service events are interacting with the lsp requests here, some explanation might be good

Copy link
Member

@davidwengier davidwengier left a comment

Choose a reason for hiding this comment

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

Makes sense in general

@CyrusNajmabadi CyrusNajmabadi marked this pull request as ready for review September 30, 2020 01:32
@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner September 30, 2020 01:32
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.

mainly lgtm!
one request, a few comments
Could you verify in a local razor file that other (non-diagnostic) c# LSP features work (e.g., go to definition) when the LSP razor editor flag is set? I assume diagnostics won't until @TanayParikh completes the work for pull diagnostics, but I want to make sure that my assumption that the rest of the c# features work w/out the RazorLanguageClient is true

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.

missed a couple comments in the first pass

@ghost
Copy link

ghost commented Sep 30, 2020

Hello @CyrusNajmabadi!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Auto-approval

@ghost ghost merged commit 3911ee0 into dotnet:master-vs-deps Oct 1, 2020
@ghost ghost added this to the Next milestone Oct 1, 2020
dibarbet added a commit to dibarbet/roslyn that referenced this pull request Oct 1, 2020
…stics"

This reverts commit 3911ee0, reversing
changes made to 60ae83d.
ghost pushed a commit that referenced this pull request Oct 2, 2020
Revert "Merge pull request #47914 from CyrusNajmabadi/lspDiagnostics"
CyrusNajmabadi added a commit to CyrusNajmabadi/roslyn that referenced this pull request Oct 5, 2020
dibarbet pushed a commit that referenced this pull request Oct 7, 2020
@Cosifne Cosifne modified the milestones: Next, 16.9.P1 Oct 12, 2020
@CyrusNajmabadi CyrusNajmabadi deleted the lspDiagnostics branch April 11, 2021 18:24
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants