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
Admittedly, I am not terribly familiar with SASS, I was wondering if it would be possible to add a flag to the compiler to, instead of substituting variables in, do the following:
Additional details, such as what to do with functions like darken, would need to be worked out, however I think this feature would be highly useful. This is especially important in CDN environments, such as Materialize, where the user must download the source, recompile it themselves, then host it themselves if they want to do something like change a color.
The text was updated successfully, but these errors were encountered:
The semantics of Sass variables are very different than those of CSS custom properties. For one thing, Sass variables are interpreted procedurally, so that a change later in the stylesheet won't affect earlier uses of the variable. They also support functions, operations, mixins, and control structures in a way that's impossible to emulate with custom properties. You're better of choosing between the two for use-cases where each one makes sense.
Hello,
Admittedly, I am not terribly familiar with SASS, I was wondering if it would be possible to add a flag to the compiler to, instead of substituting variables in, do the following:
to
Additional details, such as what to do with functions like
darken
, would need to be worked out, however I think this feature would be highly useful. This is especially important in CDN environments, such as Materialize, where the user must download the source, recompile it themselves, then host it themselves if they want to do something like change a color.The text was updated successfully, but these errors were encountered: