-
Notifications
You must be signed in to change notification settings - Fork 199
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
Clean up extension methods in MS.CA.Razor.Workspaces #10670
Clean up extension methods in MS.CA.Razor.Workspaces #10670
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GitHub borked on this PR, so I don't know that I got all of it, but I saw the important parts.
My only feedback is bikeshedding the meaning of words like "Collapsed" and "Empty", and whether we can just remove logging. I've been converting one of the document mapping methods from TextEdit to TextChange, and thats what I've been doing as I've been creating/modifying these sorts of extension methods.
Love the change overall though, and very excited to resolve the conflicts in my current branch 😁
...osoft.AspNetCore.Razor.LanguageServer/CodeActions/Razor/CreateComponentCodeActionResolver.cs
Outdated
Show resolved
Hide resolved
src/Razor/src/Microsoft.CodeAnalysis.Razor.Workspaces/Extensions/LinePositionExtensions.cs
Outdated
Show resolved
Hide resolved
src/Razor/src/Microsoft.CodeAnalysis.Razor.Workspaces/Extensions/ProjectExtensions.cs
Outdated
Show resolved
Hide resolved
src/Razor/src/Microsoft.CodeAnalysis.Razor.Workspaces/Extensions/RazorCodeDocumentExtensions.cs
Outdated
Show resolved
Hide resolved
src/Razor/src/Microsoft.CodeAnalysis.Razor.Workspaces/Extensions/VsLspExtensions_Range.cs
Outdated
Show resolved
Hide resolved
...oft.VisualStudio.LanguageServices.Razor/LanguageClient/Cohost/CohostSignatureHelpEndpoint.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love it
As I started looking at co-hosting support for Go to Definition, I noticed that our extension methods for working with LSP types had started to grow out of control. This is even more awkward now, since we've got two sets of LSP types in Razor for co-hosting: Microsoft.VisualStudio.LanguageService.Protocol and Roslyn.LanguageService.Protocol.
My commit history starts out helpful, but by the end, the commits are quite a bit bigger as they focus specifically on LSP extensions and updating relevant calling code.