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
CSS comments (/**/) are parsed and interpolation is performed within them. This is a rational and good thing, unless you want to comment out SCSS code without using SCSS comments (//).
Now, if one uses --style=compressed that won't save the comments, parsing them isn't very useful (although existing code could behave differently if they're not parsed anymore).
I suggest adding a new parameter --skip-comments or similar, that simply disables parsing of CSS comments. You can use it if you want to be able to use any kind of commenting to disable code. Especially if you also use --style=compressed.
It's generally not a good practice to add flags that change the behavior of the language itself, because it makes it easier to write stylesheets that aren't portable from one user's Sass installation to another's. Since it's also possible to comment out blocks of Sass code with silent comments, which many text editors have built-in macros for, I don't think it's worth the extra complexity and unportability.
CSS comments (
/**/
) are parsed and interpolation is performed within them. This is a rational and good thing, unless you want to comment out SCSS code without using SCSS comments (//
).Now, if one uses
--style=compressed
that won't save the comments, parsing them isn't very useful (although existing code could behave differently if they're not parsed anymore).I suggest adding a new parameter
--skip-comments
or similar, that simply disables parsing of CSS comments. You can use it if you want to be able to use any kind of commenting to disable code. Especially if you also use--style=compressed
.WDYT?
Related: #1123
The text was updated successfully, but these errors were encountered: