microsoft / microsoft/language-server-protocol
Define a protocol for syntax tokens
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
Is my reading correct, that semantic tokens only add additional information to tokens?
Can we trust that the clients will render keywords correctly, if they already have a syntax highlighter (frequently regexp based).
If that's the case, should there be an option to "unset" a type. Just as an example, if you have #ifdefs you could think of giving the LSP server the option of removing syntax coloring from inactive code segments by giving it the token-type None.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the semantic-token behavior and client rendering assumptions raised in the issue, focusing on inactive #ifdef regions and the proposed token type None. Done means the protocol explicitly resolves whether semantic tokens can unset existing syntax coloring and documents the expected client behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100