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'd argue you should have @include at the beginning as they tend to be a base that is added to. If they come at the end of the selector the styles will overwrite the ones you've declared on that declaration already.
The text was updated successfully, but these errors were encountered:
Like many things put forth by styleguides, I think this too comes down to a matter of perspective. On the flip side, putting @include before the rest of your properties could result in another developer, unfamiliar with the content of the mixin, coming in and unintentionally overriding a property crucial to the intent of the mixin.
I'd argue you should have
@include
at the beginning as they tend to be a base that is added to. If they come at the end of the selector the styles will overwrite the ones you've declared on that declaration already.The text was updated successfully, but these errors were encountered: