You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Whle #15 seems to be fixed, I'm not able to assign pcss to the config array, even is is a perfect valid postcss extension suggested for any postcss file since enables vscode completation, stylelint validations and postcss plugin support.
Expected behavior
No warning about pcss extensions
Screenshots
Additional Info
Some of the accepted values are not extensions at all, like postcss and stylus are not file extensions, they are language IDs and their relative extensions are .pcss and .styl. Language IDs and file extensions are two completely different things in vscode.
Warning
By adding postcss to the list it works for all files using postcss id, indipendently from their extension. It looks like a mispelled setting name since seems to work with languages and not file extensions
Solution
Rename cssvar.extensions into cssvar.languages or make it work with file extensions and not language IDs.
The text was updated successfully, but these errors were encountered:
Describe the bug
Whle #15 seems to be fixed, I'm not able to assign
pcss
to the config array, even is is a perfect valid postcss extension suggested for any postcss file since enables vscode completation, stylelint validations and postcss plugin support.To Reproduce
Steps to reproduce the behavior:
Expected behavior
No warning about
pcss
extensionsScreenshots
Additional Info
Some of the accepted values are not extensions at all, like
postcss
andstylus
are not file extensions, they are language IDs and their relative extensions are.pcss
and.styl
. Language IDs and file extensions are two completely different things in vscode.Solution
Rename
cssvar.extensions
intocssvar.languages
or make it work with file extensions and not language IDs.The text was updated successfully, but these errors were encountered: