Fix InlineDocBlockSniff for abstract/interface methods#51
Merged
dereuromark merged 1 commit intomasterfrom Mar 27, 2026
Merged
Conversation
- Skip methods without a body (abstract/interface) to avoid scanning wrong token ranges that led to false "Invalid Inline Doc Block" errors - Use scope_opener directly instead of searching for curly bracket - Fix hasReturnAsFollowingToken to use === false instead of !$var
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.
Summary
scope_openerdirectly instead of searching for curly brackethasReturnAsFollowingTokento use=== falseinstead of!$varDiscovered while testing sniffs against PHP 8.4 test files with interface and abstract method edge cases.