fix: incorrect line/column tracking for selector lists #114
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.
closes #111
Summary:
The test was failing because the selector parser wasn't correctly tracking line/column positions for selector wrapper nodes in multi-selector lists.
Changes made:
- first.start from 7 → 6 (correct start position)
- second.start from 29 → 27 (correct start position)
The root cause was that after parsing the first selector and encountering a comma, the parser would skip whitespace (including newlines) but the lexer's line/column weren't being updated, causing the second selector to have incorrect position information.