[REQUEST] VSCode LSP Improvements | Semantic Highlighting

I feel there are many improvements to be made in the LSP department, and we are on a bit of a rough MVP at the current state. It does the job for development, but I haven’t seen any plans on the roadmap, so I thought I’d make some suggestions.

The current Verse LSP semantic highlighting and theming significantly harms readability:

Verse LSP has 3 main semantic tokens: “keyword”, “variable”, and “constant”. There is very little color separation for readability, and most syntax defaults to keyword.

These are some elements where it’d be nice to have separate semantic tokens:

  • Classes, properties, types, parameters, functions, variables, unused variables, braces, brackets, operators.

Real-life example
Left: Verse LSP semantic highlighting
Right: NextJS semantic highlighting

This would not only be a massive QoL improvement, but also give us the freedom to use any theme we prefer, and not have it suffer from poor semantic tokenization.

Thanks!

@kasparugc Thank you for your feedback. While I cannot guarantee a response, I can confirm that this has been forwarded to the appropriate team.