feat: upgrade API in order to reflect upcoming complexity in CSS selectors #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: API is backwards incompatible
Change: Instead of separate fields for
tag
,ids
,classNames
,attributes
,pseudoClasses
andpseudoElement
there is a single fielditems
which contains list of those entities. For ids there is a newId
entity type, for class names there is a newClassName
entity type, for pseudo elements there is newPseudoElement
entity name.Why: In the new CSS standard (selectors-4) and some CSS drafts the order of items in a CSS rule became important. Also pseudo element got arguments.
Example 1
Before:
After:
Example 2
Code:
Before:
After: