-
Notifications
You must be signed in to change notification settings - Fork 676
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
Support inlay hints #5107
Support inlay hints #5107
Conversation
This will need OmniSharp/omnisharp-roslyn#2357 to be merged, and I still need to write some integration tests covering the new feature. Some screenshots: |
I just wanted to come here and thank you guys for all your efforts. the inlay hints was one of the main reasons I still have Rider installed on my machine |
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.
Did you test this with a Razor scenario?
Do we need to filter out Razor generated documents?
https://github.com/OmniSharp/omnisharp-vscode/blob/84f1d5ab16718c2e0ad91e732770515500a8113e/src/features/virtualDocumentTracker.ts#L25-L39
Or handle mapping location information to Razor documents by passing it through the LanguageMiddleware?
https://github.com/OmniSharp/omnisharp-vscode/blob/84f1d5ab16718c2e0ad91e732770515500a8113e/src/features/referenceProvider.ts#L25-L27
Closes OmniSharp/omnisharp-roslyn#1932. Implements the new inlay hint api for vscode, now that it's stable and in LSP. Tests still need to be written.
I think we should probably avoid razor documents for now, until @NTaylorMullen has a chance to test it out and make sure that everything is working as expected. |
aeb6ebd
to
6141d88
Compare
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.
Suggestion on how to make the test more consistent
hey. I really need this feature even if it's in beta. can someone help me on how to use this branch in vscode? I could be helpful with my bug reports later :p |
@JoeRobich we'll see, but locally the test doesn't even require that the file is open at all. Something else is happening. |
Check out the branch and build it. |
yes, trying. but my npm gives out too many errors :(
Nevermind. I successfully built the package and tested it and THANKS! I wish I could somehow support you guys because this feature made me completely delete Rider and switch to vscode for good :) |
Co-authored-by: Joey Robichaud <joseph.robichaud@microsoft.com>
Co-authored-by: Joey Robichaud <joseph.robichaud@microsoft.com>
Hey, umm , this is written "Merged" does it mean It's officially gonna go to the master branch now? Or just to the master of this fork? Sorry I don't know much about GitHub |
This isn't a fork, it's the main repository. And yes, it has been merged to master and will be in the next release of omnisharp vscode. |
Thanks, yeah, figured that out by some research afterwards :D thanks. And the feature is really great! You guys are breaking the boundaries between vscode and Rider for dotnet!
|
@somedeveloperhappy Do you have either of these options enabled? Async completion should help with completion performance. "omnisharp.enableAsyncCompletion": true,
"omnisharp.enableImportCompletion": true, |
Closes OmniSharp/omnisharp-roslyn#1932. Implements the new inlay hint api for vscode, now that it's stable and in LSP. Tests still need to be written.