microsoft / microsoft/vscode-powerquery
[Enhancement] Use LSP based semantic token functionality
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 108
- Forks
- 25
- Avg merge
- 8d 22h
- Merged PRs (30d)
- 2
Description
Our initial semantic token handling was implemented before it was fully supported in the vscode lsp framework.
Look for implementation examples using:
connection.languages.semanticTokens.on
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 locating the existing semantic token handling in the TypeScript extension and compare it with the LSP 3.17 textDocument/semanticTokens specification. Search for implementation examples using connection.languages.semanticTokens.on; done means the existing handling uses the supported LSP semantic token functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100