-
Notifications
You must be signed in to change notification settings - Fork 86
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
tokens in SemanticHighlightingInformation should be optional #133
Comments
Nice catch! A PR would definitely be accepted! |
Thanks @Marwes, Could a new version be released so these changes can be used? |
Is this an earlier version of the semantic tokens proposal located: https://github.com/microsoft/vscode-languageserver-node/blob/dbaeumer/semanticTokens/protocol/src/protocol.sematicTokens.proposed.ts ? |
I'm not entirely sure but but I think that first link might be a vscode internal protocol, not a proposal for LSP. The original PR for the semantic highlighting at microsoft/vscode-languageserver-node#367 still remains the same. |
The latest proposed for 3.16 is https://github.com/microsoft/vscode-languageserver-node/blob/master/protocol/src/protocol.sematicTokens.proposed.ts just updated a few days ago |
Hi,
I am currently working on a PR (autozimu/LanguageClient-neovim#954) to support the proposed semantic highlighting protocol for LanguageClient-neovim. I noticed that the
SemanticHighlightingInformation
type'stokens
field should be optional but is currently not:Theres a document describing the protocol here: https://github.com/microsoft/vscode-languageserver-node/blob/5a9b33c23de84c3341e011e79221795a8059375b/protocol/src/protocol.semanticHighlighting.proposed.md
It shows that the tokens field can be omitted for a line if there are no tokens to highlight there. So the tokens field should be a
Option<Vec<SemanticHighlightingToken>>
instead.Currently this is a problem since I can't deserialize the following message from eclipse/eclipse.jdt.ls because it omits
tokens
:Just posting as a issue for now, I can open up a PR if that's preferred.
The text was updated successfully, but these errors were encountered: