Replacing class method visibility doesn't work without previous node' attributes in format-preserving pretty printing#1116
Closed
maks-rafalko wants to merge 1 commit intonikic:masterfrom
Conversation
This was referenced Oct 14, 2025
Owner
|
This is intended behavior. Formatting preservation requires the origNode attribute to be set. This is intended to be achieved through in-place modification, though creating a new one and copying origNode works as well. |
maks-rafalko
added a commit
to infection/infection
that referenced
this pull request
Oct 21, 2025
Format-preserving pretty printing is hard :| After a week of evenings of debugging, here we go. https://github.com/nikic/PHP-Parser/blob/master/doc/component/Pretty_printing.markdown#formatting-preserving-pretty-printing Why is this needed? - To correctly highlight mutated code in PhpStorm Plugin (requested here: #2425 (comment)) - To have original code in code diffs for each Mutant. Previously, the code was reformatted by PrettyPrinter from `php-parser` Instead of 1000 words, examples: Before: ```diff @@ @@ } public function logVerbosityDeprecationNotice(string $valueToUse): void { - $this->logger->notice('Numeric versions of log-verbosity have been deprecated, please use, ' . $valueToUse . ' to keep the same result', ['block' => true]); + $this->logger->notice('Numeric versions of log-verbosity have been deprecated, please use, ' . $valueToUse . ' to keep the same result', []); } public function logUnknownVerbosityOption(string $default): void { ``` After: ```diff @@ @@ { $this->logger->notice( 'Numeric versions of log-verbosity have been deprecated, please use, ' . $valueToUse . ' to keep the same result', - ['block' => true], + [], ); } ``` As you can see, previously Infection **modified** the source code formatting, then created a Mutant, and then compared modified original code with mutant. Now, original code is compared with a mutant as is - we ONLY change the mutated node. No more reformatting. This gives us much more readable and clear diffs. Long multiline arrays are no longer changed to lengthy one-liners. ---- During implementation, I found several bugs in `php-parser`: - nikic/PHP-Parser#1115 - nikic/PHP-Parser#1116 - nikic/PHP-Parser#1117 - nikic/PHP-Parser#1119 These are not blockers, but interesting to see the answers from Nikita. I have a feeling that either these are bugs or we don't use nodes replacements correctly (probably we should do them in-place) - let's see. ---- - [x] check how HTML report works after these changes
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
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?