feat: implement syntax stringifier #5
Merged
Conversation
This file contains 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
|
postcss 8.4 is out, which now has stringifier types... but i missed the i've opened postcss/postcss#1681 which now blocks this |
Pull Request Test Coverage Report for Build 1504286696
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have implemented a basic stringifier which rebuilds the original expression text.
In order to retrieve the original text, we have to make use of
rawson the root node it seems. This could be replaced if some other plugin decides to mutate our placeholder comments, so in those cases we will leave the comments as-is.CURRENTLY BLOCKED: This depends on postcss/postcss#1675 being merged and released.BLOCKED BY: postcss/postcss#1681