fix: node end offset location #1879
Merged
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.
This PR addresses the issue of
source.end.offsetbeing off by one.The problem stemmed from direct use of the token location as the offset when resolving line and column with
getPosition(), which worked well forstart.offset, but should point to the index immediately after the node for theend.offsetto ensure thatsource.slice(start.offset, end.offset)provides the correct node source.The solution is straightforward: I've reviewed the parser's instances where the end offset is set and made a simple adjustment off adding 1 (except the final root location that works as expected).
There are still 30 failing tests originating from postcss-parser-tests that needs to have their expectation JSON adjusted - I probably need some help making that change, thank you in advance!