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
{{ message }}
This repository has been archived by the owner on May 31, 2021. It is now read-only.
Since this highlighting is fork of SCSS highlighting I didn't change syntax scope from source.scss. I did this for other Sublime Text plugins compatibility. They are relies on scope and know nothing about source.postcss scope. This bring up issue when comments settings for PostCSS and comments settings for SCSS is conflicted and Sublime Text uses only PostCSS settings (at least in my setup). This is not breaks SCSS, because it's standard CSS comments (/* */), but it's not user expecting.
I'm waiting for adding PostCSS compatibility to following plugins in order to fix this issue:
Since this highlighting is fork of SCSS highlighting I didn't change syntax scope from
source.scss
. I did this for other Sublime Text plugins compatibility. They are relies on scope and know nothing aboutsource.postcss
scope. This bring up issue when comments settings for PostCSS and comments settings for SCSS is conflicted and Sublime Text uses only PostCSS settings (at least in my setup). This is not breaks SCSS, because it's standard CSS comments (/* */
), but it's not user expecting.I'm waiting for adding PostCSS compatibility to following plugins in order to fix this issue:
CSSComb 4.0 releaseDoesn't matter because for sorting reason may be replaced by sublime-postcss-sorting which have better sorting abilities.The text was updated successfully, but these errors were encountered: