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
Add checkContextFunctionalPseudoClasses: []
to selector-max-id
#7380
Conversation
🦋 Changeset detectedLatest commit: 9b6b8d9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
@brigitamaria Thanks for the PR! The draft is looking good.
config: [ | ||
0, | ||
{ | ||
includeContextFunctionalPseudoClasses: [':global'], |
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.
includeContextFunctionalPseudoClasses: [':global'], | |
includeContextFunctionalPseudoClasses: [':--foo'], |
Let's use custom pseudos in the test and documentation to avoid using non-standard syntax.
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.
Updated f310fa7 😄 thanks for your feedback!
includeContextFunctionalPseudoClasses: []
to selector-max-id
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.
@brigitamaria Thank you for the PR.
I've requested some changes to the tests and docs to align with our conventions.
includeContextFunctionalPseudoClasses: []
to selector-max-id
checkContextFunctionalPseudoClasses: []
to selector-max-id
On revisiting this issue, I realised we should call the option I've committed my suggestions and renamed the option. PR LGTM, but it could do with a second pair of eyes. |
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.
[suggest] Thank you for the pull request. LGTM too.
In addition, I suggest the refactoring to make the complex if
condition a bit more readable:
- Move the
isContextFunctionalPseudoClass
call intoisIgnoredContextFunctionalPseudoClass
- Rename
isIgnoredContextFunctionalPseudoClass
toisUnignoredContextFunctionalPseudoClass
- Check a node's type in
isCheckedContextFunctionalPseudoClasses
- Rename
isCheckedContextFunctionalPseudoClasses
toisCheckedContextFunctionalPseudoClass
@ybiquitous Great suggestions. I've made the changes. |
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.
LGTM!
Proof of concept for #7364
Yes, the documentation needs to be updated and I still have a type error that I'd like to discuss