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
Probably it would be helpful to document that @import statement is evaluated "right away" before anything else (specifically mixins). Or, in other words, that it's a sort of "static" statement and it's evaluated exactly where it appears. E.g. when we write something like:
.mixin() {
@import"something";
}
the code is literally equal to:
.mixin() {
<the content of the "something" file>
}
thus mixin parameters cannot be interpolated in such import statements, because the import is unconditionally expanded/resolved at the point of the mixin definition (and not when we call/invode that mixin) when and where the mixin parameters values are yet unknown.
The text was updated successfully, but these errors were encountered:
Specifically #2772.
Probably it would be helpful to document that
@import
statement is evaluated "right away" before anything else (specifically mixins). Or, in other words, that it's a sort of "static" statement and it's evaluated exactly where it appears. E.g. when we write something like:the code is literally equal to:
thus mixin parameters cannot be interpolated in such import statements, because the import is unconditionally expanded/resolved at the point of the mixin definition (and not when we call/invode that mixin) when and where the mixin parameters values are yet unknown.
The text was updated successfully, but these errors were encountered: