Adopt semantic highlighting

[aeschli]

Since 1.43, VSCode themes can take advantage of semantic highlighting.

Every theme controls whether semantic tokens are enabled. So far, only built-in themes have it enabled and I filed this issue to ask you to opt-in for the Nord theme as well.

Adoption is easy and there are new cool styling possibilities.

To turn on semantic highlighting for a theme, all you have to do is put
"semanticHighlighting": true
in the theme's definition file.

There's a good chance that no further change to the theme is needed (thanks to a default mapping from semantic tokens to TextMate scopes (if not, I'd be interested to know, so I can improve the defaults further)).

But, more interestingly, themes can tune and go wild by defining new styling rules against the semantic tokens:

"semanticTokenColors": {
    "variable.readonly": "#ff0000", 
    "parameter": { "fontStyle": "underline" },
    "*.declaration:java": { "fontStyle": "bold" }
} 

Check out our Semantic Highlighting Wiki and the Semantic Highlighting Guide for more details and feel free to ping me in this issue if I can help.

Thanks for the great work and looking forward to semantic highlighting in your theme.

[arcticicestudio]

Hi @aeschli 👋, thanks for your contribution 👍
Nice to see you involve the community even more on this way 😄

I read release notes for my personal use as well as for changes related to the theme API every time a new VS Code version gets published. Therefore I've already created a note in the repository backlog to learn more about semantic highlighting. Also enabled it locally some weeks ago to take a quick look and disabled it again since it broke a lot of colors, but after reading through the latest change logs and PRs in the VS Code repository I guess this is fixed by now.

There are currently a lot other tasks for other projects and Nord ports as well as for my job due to the current world health situation, but I definitely planned to adapt to it within the next weeks.

[nomenon]

https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.21.19-beta1

[arcticicestudio]

@nomenon How is this related to this issue?

---

Status report so far after enabling semantic highlighting on my local machine and using it for some weeks: Works fine for different languages. I haven't had any issues or noticed any broken highlighting. Sometime it takes some seconds until the highlighting is updated, but this also depends on the current workload of the system as well as the project size and number of lines in the opened files.

I'll continue to use it locally until the weekend, but I guess it should be fine to merge the change and release a new extension version to roll it out to the users for more feedback.