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
Should we add the selector-no-union-class-name rule to disallow inline & in CSS selectors? This would prevent incomplete selectors in SCSS files, but still allow combining selectors.
For example:
.class {
&-union { /* not allowed */ }
&.child-class { /* this is okay */ }
}
The text was updated successfully, but these errors were encountered:
I agree this can be problematic in large blocks where one can lose sight of the prefix, and there is no way to define what is the right size of block for it to be ok. Having a rule in the tooling means it's one less thing to think about when reviewing so I'm for it 👍
💯 , I find those a much harder to search for, and even when just reading it introduces a tiny bit of friction. I don't really see any significant benefit to them.
Should we add the
selector-no-union-class-name
rule to disallow inline&
in CSS selectors? This would prevent incomplete selectors in SCSS files, but still allow combining selectors.For example:
The text was updated successfully, but these errors were encountered: