Repository navigation
[CodeQuality] Skip trailing comment after return in WillReturnCallbackFallbackToReturnFalseRector - #800
Merged
Conversation
…kFallbackToReturnFalseRector
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.
Fixes rectorphp/rector#9929
When
return true;is followed by a trailing comment, PHP-Parser turns the comment into a trailingNopstatement, so it becomes the closure's last statement. The rule only checked the raw last statement forReturn_, missed it, and wrongly appended areturn false;fallback after an already-terminating return.Fix skips trailing
Nopstatements before checking whether the closure already ends with a return.Before:
Added a skip fixture reproducing the issue.