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

Features/lsp support liveshare2 #35214

Merged

Conversation

dibarbet
Copy link
Member

@dibarbet dibarbet commented Apr 23, 2019

This copies and creates liveshare LSP handlers so that they can be exported from roslyn instead of from liveshare.

The implementation of all the handlers is copied directly from liveshare. For now, I'll be leaving that as-is and later will be going 1 by 1 to clean them all up once liveshare is working from roslyn. Mainly would like feedback on the structure (handlers, location of classes, etc)

Where possible, I've moved the implementation into the features layer. However, some have dependencies on the UI, so I've kept those in the VS language services layer until we can remove those dependencies.

TODO - more tests
TODO - get actual release build of MS.VS.LanguageServer.Protocol (so CI passes)
TODO - Wait for fixed liveshare nuget pkg

@dibarbet dibarbet requested review from heejaechang and a team April 23, 2019 18:07
@dibarbet dibarbet force-pushed the features/lspSupport_liveshare2 branch from 67fb44c to d252a1a Compare April 23, 2019 18:34
/// Handles the get code actions command.
/// </summary>
[Shared]
[ExportLspMethod(LSP.Methods.TextDocumentCodeActionName)]
Copy link
Contributor

Choose a reason for hiding this comment

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

name for export and interface, we probably need to change later after design meeting.

var description = await completionService.GetDescriptionAsync(document, selectedItem, cancellationToken).ConfigureAwait(false);

LSP.CompletionItem resolvedCompletionItem;
if (clientCapabilities?.HasVisualStudioLspCapability() == true)
Copy link
Contributor

Choose a reason for hiding this comment

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

so, this without VS extension (I think we should rename it LSP.Extension not VS Extension) we return RoslynCompletionItem? not regular LSP completion Item?

@JoeRobich JoeRobich force-pushed the features/lspSupport branch from e561eb8 to 0129409 Compare May 3, 2019 14:13
@dibarbet dibarbet requested review from a team as code owners May 8, 2019 21:06
@dibarbet dibarbet force-pushed the features/lspSupport_liveshare2 branch from 3a3460e to e42a4b0 Compare May 14, 2019 17:57
@dibarbet dibarbet force-pushed the features/lspSupport_liveshare2 branch from e42a4b0 to 908819f Compare May 14, 2019 21:46
@dibarbet dibarbet removed request for a team May 15, 2019 22:29
@dibarbet dibarbet merged commit 0fe435e into dotnet:features/lspSupport May 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants