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
The migrator should add additional @use rules to ensure that selectors being extended are upstream of the extending selector.
An internal team ran into this issue when migrating. The compiler saved them for extended placeholder selectors, but not for a concrete selector that was also present within the same stylesheet as the @extend (which they didn't notice until their screenshot tests failed).
The text was updated successfully, but these errors were encountered:
We need this now - why has this not been updated since 2019? We get the feeling its still better to keep the old import system, until everything is fully ready to be migrated, since we have several very large complex angular projects.
The migrator should add additional
@use
rules to ensure that selectors being extended are upstream of the extending selector.An internal team ran into this issue when migrating. The compiler saved them for extended placeholder selectors, but not for a concrete selector that was also present within the same stylesheet as the
@extend
(which they didn't notice until their screenshot tests failed).The text was updated successfully, but these errors were encountered: