Replacing class method visibility doesn't work without previous node' attributes in format-preserving pretty printing #1116
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 finding is related to #1115
(It's a bug-report with test reproducer, not the fix or feature implementation)
at Infection, we do a lot of nodes replacements during the Mutation Testing process.
For example (see tests in this PR), we replace
public function ...withprotected function ...class method visibility modifier.However, unlike with other replacements, this one for some reason requires
$replacedNode->getAttributes()to be passed when the new Node is created:Replacement:
Please note how we pass
$replacedNode->getAttributes()to the the createdClassMethodnode. If I omit it, then we have a completely broken formatting:But when I pass
$previousNode->getAttributes(), the diff is clear and correct:What is not clear:
$replacedNode->getAttributes()while in other cases (like here) we don't need to pass it?