Skip AddMissingVarNameFixer for property assignments#45
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
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.
AddMissingVarNameFixergrabbed the wrong token as the variable name in two cases.Property assignment
Above a
$this->prop = ...assignment, the nextT_VARIABLEis$this, so the fixer wrote@var int $this.final class SomeClass { public function run() { - /** @var int */ + /** @var int $this */ $this->value = 1000; } }Now skipped when the variable is followed by
->(property access).Annotations (regression guard)
Docblock annotations like
@Entityor@\Doctrine\ORM\Mapping\Entitywere already skipped (the regex requires a literalvar), but this had no test. Added a fixture to lock the behavior — these are left untouched: