Having @include at the beginning of a selector vs the end
Open
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the repository's existing guidance for Sass @include placement and compare it with the proposed beginning-versus-end convention. Since no file or test is named, first identify where this style guidance is maintained; done means reaching a documented, agreed ordering rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sass
- Domain
- frontend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100