Fix function call detection to exclude non-function tokens #279
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.
The helper function
getFunctionIndexForFunctionCallArgument()
(and by associationisTokenInsideFunctionCallArgument()
) tries to return the position of the function name token for a function call argument (eg: in the expressiongreet($user)
it would return the token position forgreet
for the variable$user
). It does this by finding the nearest enclosing parentheses and then looking at the non-whitespace token that comes before it. If that token does not look like a function definition, then it assumes it is a function call.Unfortunately, this is too naive and will consider things like equals signs as function calls.
In this PR we modify the function to also reject anything not in PHPCS's list of valid function call token types and anything not in the same scope level.
Fixing this also fixed another bug, which had not been caught because one of the for loop tests was mis-written. Some variables inside for loops were being considered reads as well as writes.
Fixes #277