-
Notifications
You must be signed in to change notification settings - Fork 203
Enable CSharp Semantic tokens in VSCode #4323
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
Comments
VSCode added the API's we need, now available on insiders. microsoft/vscode@f101028 |
@NTaylorMullen and Ryan, seeing that VS Code has added the APIs, I'm interested to know how much work you expect wiring up semantic highlighting in VS Code to be, and if it's something you can reasonably see an outside contribution for? |
We're still trying to solidify our current C# semantic token strategy so we aren't fully ready to accept a contribution yet but love that you're digging into the guts of Razor! |
Understandable, thanks for letting me know! |
Any updates? |
This was fixed in dotnet/vscode-csharp#6489 |
Right now CSharp semantic tokens are not enabled in VSCode because there's no way for use to call through to the CSharp LanguageServer. Other endpoints doing similar things use the
vscode.execute<Blank>Provider
commands, but no such command exists for Semantic Tokens because it's still a "draft" part of the LSP spec.The text was updated successfully, but these errors were encountered: