-
Notifications
You must be signed in to change notification settings - Fork 117
Bump version of vscode-css-languageservice to 5.1.4 #333
Bump version of vscode-css-languageservice to 5.1.4 #333
Conversation
@florianbuehler are you sure this fixes your issue? can you show a before and after screenshot? |
For updating syntax see https://github.com/styled-components/vscode-styled-components/blob/master/CONTRIBUTING.md#adding-syntax For an example see my “fix urls” PR We extend from the builtin VSCode css syntaxes file so take a look here to see what you need https://github.com/microsoft/vscode/blob/main/extensions/css/syntaxes/css.tmLanguage.json the first thing I would do is search for “accent-Color” in that file I linked and see how it matches up with our syntax file (i.e where should it be) |
@jasonwilliams thank you for the hint! You are right, bumping the package version is not fixing the highlighting: |
I will also look into https://github.com/microsoft/vscode/blob/main/extensions/css/syntaxes/css.tmLanguage.json so we also get the color highlighting :) |
That’s actually quite interesting, I didn’t expect our version to be having an affect on the typescript plugin. https://github.com/microsoft/typescript-styled-plugin/blob/main/package-lock.json#L12 Maybe it does need bumping after all |
I’m going to merge this and we should continue discussion in the issue |
I thought there was an issue for syntax highlighting but there isn’t, feel free to make one @florianbuehler |
@jasonwilliams I just opened one: #335 |
Currently the syntax highlighting is not working for some of the newer CSS entities (e.g. accent-color).
This is because
accent-color
was only added in vscode-custom-data@0.3.5 and that package version is only used since vscode-css-languageservice@5.1.4. Therefore simply upgrading the package version will fix that issue.