fix: manipulation of node structures, proper stringifying #73
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 contains:
Breaking Changes?
If yes, please describe the breakage.
Please Describe Your Changes
This PR fixes #69, wherein manipulating the child nodes for a particular node (in this case a
Func
node) did not reflect in stringifying of the node. This solution was derived from the following test code:The result of which is now:
Note that the
parent
property is being set in the code above, whereas the referenced issue did not set the property. This is required for PostCSS internals to accurately determineraws
values to render.Since we were previously only rendering the
params
property of functions (which is a string reference to unparsed function parameters), some additional work had to be performed to correctly capture and render spacing around and within the function parens. I believe this PR covers all of the various cases we may encounter.