-
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
Add co-hosting support for hover #11150
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.
Nifty raw content validation
src/Razor/src/Microsoft.CodeAnalysis.Remote.Razor/Hover/RemoteHoverService.cs
Outdated
Show resolved
Hide resolved
Rework the logic in RemoteHoverService. It isn't necessary to try and map the host document index to C#, since `GetPositionInfo(..., preferCSharpOverHtml: true)`already does that for us.
src/Razor/src/Microsoft.CodeAnalysis.Remote.Razor/Hover/RemoteHoverService.cs
Outdated
Show resolved
Hide resolved
FYI I merged #11151 so you'll want to merge main, as |
No worries! Thanks for the heads up! I'll get it fixed up. |
Fixes #10839
Now that all of the infrastructure is in place, adding a co-hosting endpoint and remote service for Hover is mostly boilerplate. Similar to the signature help endpoint, the result type might be a Roslyn LSP Hover or a VS LSP Hover. The remote service always returns a Roslyn LSP Hover, but HTML will return a VS LSP Hover. So, we join the possibilities together with a SumType.