fix(parser): correct skip_until TextSpan range #9611
+26
−3
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
adjusted skip_until to derive the span directly from the token text range (excluding trivia) and added a focused unit test that checks the returned TextSpan covers all skipped tokens and starts at the first non-trivia character.
Type of change
Please check one:
Why is this change needed?
Before this change, skip_until was computing SkippedElement spans from the raw parser offset, including leading trivia and stopping inside the token text. As a result, diagnostics for skipped tokens were slightly shifted and inconsistent with other span calculations.