Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Having @include at the beginning of a selector vs the end #10

Open
dan-gamble opened this issue Jan 28, 2016 · 1 comment
Open

Having @include at the beginning of a selector vs the end #10

dan-gamble opened this issue Jan 28, 2016 · 1 comment

Comments

@dan-gamble
Copy link

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.

@mikefowler
Copy link
Contributor

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.

¯\_(ツ)_/¯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants