-
-
Notifications
You must be signed in to change notification settings - Fork 927
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
Added: selector-max-type
rule
#2665
Conversation
1f5a128
to
3110ec4
Compare
Yes, absolutely. Rules should be most restrictive by default (when it comes to standard CSS), and then made more permissive with options. Let's only add a
Shouldn't this whole selector be ignored by the rule as it's non-standard? We should check that resolved selectors are standard. If not, return early. |
Non-standard selectors should be ignored, and tests for them should be accepted. |
@hudochenkov Updated this one.
|
selector-max-type
ruleselector-max-type
rule
@hudochenkov Once you've approved my commits. I'll squash them and rebase this off |
Why we don't ignore non-standard selectors?
@hudochenkov Oops. I missed that one. Changed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work!
2836bd1
to
554a5dd
Compare
554a5dd
to
184043d
Compare
|
#2528
No, it's self explanatory.
Need resolve:
html { --foo: 1px; }
andhtml { --custom-property-set: {} }
should be rejected? I think yes, because we can havehtml { --some-here: 1px; --custom-property-set: { color: red; display: block; }; color: red;}
Later we can add optionignoreContaintCustom
(or best name for this purpose).@for $n from 1 through 5 { .foo-#{$n} { div { content: \"#{$n}\"; } } }
) output error.foo-#{$n} div
, it is valid because we containdiv
, but message is very weird. It is normal or not?Some tests are commented.