Reduce parser conflicts and add comprehensive tests #568
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.
Summary
Key grammar changes
style_rule,keyframes,declarations)pseudo_class_selectorFUNCTION alternatives usingrelative_selector_listattribute_selectorusingattr_matcher_parthelperSEMI_COLON?frombrace_blockand other rulescomplex_selectorusinglist()instead of two alternativesTest coverage
New comprehensive tests covering:
!importantNotes
The remaining 28 shift/reduce conflicts are structural - they stem from
WSbeing both a meaningful token (value: | WS { Whitespace }) and an optional separator (WS?). Further reduction would require fundamental changes to whitespace handling.