custom themes lack match and case syntax highlighting

[scarf005]

default themes and github themes support match case syntax, however majority of other themes does not support them out of the box.

running Inspect editor tokens and scopes shows result like this:

could there be any way to overwrite custom themes to support match case?
(using editor.tokenColorCustomizations for every single themes would too much work)

Originally posted by @scarf005 in #1215 (comment)

[rchiodo]

I'm not sure what the ask is here? Themes can provide their own colors for keyword.

Here's an example:

  "editor.semanticTokenColorCustomizations": {
    "[Default Light+]": {
      "rules": {
        // Make keywords green
        "keyword": "#00ff26"
      }
    }
  },

Which produces:

Are you asking for a different token specific to 'match' and 'case'?

[scarf005]

then why are match/case not identified as keyword?

[rchiodo]

Do you have a specific case where that happens? I can't repro your first screen shot.

[congard]

It seems that in certain themes, such as for example One Monokai, Monokai Night or Darcula match and case are not identified as keyword. Is it an issue with pylance or with the aforementioned themes?

Darcula:

Dark Modern:

[rchiodo]

Pylance (and the tmlanguage grammar that ships with VS code) knows nothing of the theme being used. My guess is that the theme is not defining a color for the token, or is overriding it somehow.

[MicBotta]

Hi,
I had the same problem with Dracula Theme and solved by enabling the Semantic Highlighting. You have to add this entries in the settings.json file:

"editor.semanticTokenColorCustomizations": {
"[Darcula Theme]": {
"enabled": true
},
},