Fix end position of rules with ownSemicon#2012
Merged
ai merged 1 commit intopostcss:mainfrom Feb 10, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See: postcss/postcss-parser-tests#28
Rules with semicolons had these assigned to
rule.raws.ownSemicolonand these are also used when serializing:postcss/lib/stringifier.js
Lines 330 to 335 in 7b02c75
However the source positions of the rules weren't adjusted after appending to
rule.raws.ownSemicolon.This change makes it so that slicing out the source range for a rule from the input CSS better matches
rule.toString()