Repository navigation
Restore shouldSkipCurrentNode guard in RectorRunner - #8591
Merged
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
1 participant
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.
An experimental commit removing the
shouldSkipCurrentNodeguard slipped into the squash-merged #8586. Without it, a rule firing on a freshly reprinted node hitsScopeFetcher::fetch()on a scopeless node and throws 'Scope not available'.This breaks behavioral tests both in rector-src (
ChangeSwitchTernaryTest) and downstream packages (e.g. rector-doctrineRemoveNullFromNullableCollectionTypeRector), which surfaced as failingpackages_testson main.Restores the 5-line guard that bails out before
refactor()when a node was already rectified by the same rule or reprinted without a refreshed scope.