Skip to content

Keep up with evolving SemanticTokens rework #4942

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.

Sign up for GitHub

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

Jump to bottom
Closed
kjeremy opened this issue Jun 18, 2020 · 1 comment · Fixed by #5930
Closed

Keep up with evolving SemanticTokens rework #4942

kjeremy opened this issue Jun 18, 2020 · 1 comment · Fixed by #5930

Comments

@kjeremy
Copy link
Contributor

kjeremy commented Jun 18, 2020

This isn't published yet but this is a good reminder that semantic tokens are still proposed and will require some fixing up for 3.16: microsoft/vscode-languageserver-node@66f91b3
@kjeremy
Copy link
Contributor Author

kjeremy commented Jul 21, 2020

This is now documented in the 3.16 protocol but vscode hasn't switched to it yet.

@kjeremy kjeremy mentioned this issue Sep 1, 2020
Merged
@bors bors bot closed this as completed in 7f79dbc Sep 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Migrate to the latest Semantic Tokens Proposal for LSP 3.16 kjeremy/rust-analyzer
1 participant
@kjeremy