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
I could not find a discussion relating to this anywhere, so I started a new one.
The SASS @import documentation clearly states that @import will soon be deprecated and removed, with several reasons given for this action. However, please consider the following setup:
In this setup, the partials use variables defined in vars.scss. With @use, this requires an extra line in each partial importing the variables again. This is especially annoying for conditional exports such as for themes, which require more lines to import.
Global imports have their uses - it should not be phased out from the spec. Although I do recognize that @import is easy to misinterpret as the non-global syntax, perhaps a new at-rule should be created that acts exactly like @import, but called @global? This way, it still allows for the desired functionality, but explicitly states that this is a global import.
The text was updated successfully, but these errors were encountered:
Hello!
I could not find a discussion relating to this anywhere, so I started a new one.
The SASS @import documentation clearly states that @import will soon be deprecated and removed, with several reasons given for this action. However, please consider the following setup:
In this setup, the partials use variables defined in
vars.scss
. With@use
, this requires an extra line in each partial importing the variables again. This is especially annoying for conditional exports such as for themes, which require more lines to import.Global imports have their uses - it should not be phased out from the spec. Although I do recognize that
@import
is easy to misinterpret as the non-global syntax, perhaps a new at-rule should be created that acts exactly like@import
, but called@global
? This way, it still allows for the desired functionality, but explicitly states that this is a global import.The text was updated successfully, but these errors were encountered: