You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Syntax highlighting is currently done on the client, which means that each client implements their own logic and deals with their own bugs. This is because LSP historically did not provide a way of highlighting a document via protocol.
Proposal
Upcoming LSP 3.16 has support for textDocument/semanticTokens which the server could implement and provide a single source of truth for how to highlight a document.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.
ghost
locked as resolved and limited conversation to collaborators
Feb 3, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current Version
Background
Syntax highlighting is currently done on the client, which means that each client implements their own logic and deals with their own bugs. This is because LSP historically did not provide a way of highlighting a document via protocol.
Proposal
Upcoming LSP 3.16 has support for
textDocument/semanticTokens
which the server could implement and provide a single source of truth for how to highlight a document.NodeJS client implementation is available in microsoft/vscode-languageserver-node#367
Related LSP methods
https://microsoft.github.io/language-server-protocol/specifications/specification-3-16/#textDocument_semanticTokens
The text was updated successfully, but these errors were encountered: