Observations between community and official

[Tatsh]

Since many of us are coming from the community version, I think many would like to see some of the features of the community version incorporated here somehow. This is comparing Dark High Contrast. In general, I think there is way too much yellow colour on screen where there used to be white in the community version.

• There is no distinction between the type and the type's type argument. Also can be considered that there is no difference between certain imports and actually built-in keywords like str, int, etc. I do not think imports should ever be the same colour of as a keyword regardless of origin or prevalence.

  

  Community:

  

  • This also makes exceptions catch the attention too much:

    

    Community:

    

• Some imports are coloured blue, others are highlighted yellow as if to be an official keyword. Some are highlighted white.

  

  Community made them all white:

  

• A change I do welcome is not having red arguments (but I do not like having Path and str being the same colour, see point 1):

  

  Community:

  

[Tatsh]

The lack of distinctions seem to be caused by the Pylance server or similar (it marks any class as the same type as str (also technically a class)). Once the server is going, it marks the types and the styles apply. I can say this did not happen in the Community Material version.

[Tatsh]

I was able to get most of what I wanted with these overrides:

  "editor.semanticTokenColorCustomizations": {
    "enabled": true,
    "rules": {
      "*.builtin": "#B2CCD6",
      "module": "#fff"
    }
  },
  "editor.tokenColorCustomizations": {
    "textMateRules": [
      {
        "scope": [
          "keyword.control",
          "markup.quote",
          "variable.parameter",
          "variable.parameter.function.language.special.self.python"
        ],
        "settings": {
          "fontStyle": ""
        }
      }
    ]
  },