Fix #48: Add array type verification before accessing index #49
Conversation
This file contains 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
Since the $rule may now be array as well as a Closure, the array type must be checked before trying to access indexes. Also, `applyFilter` calls is corrected to respect it's signature. This should fix `ErrorException Illegal string offset 'name'` being thrown. Fixes Waavi#48
alariva
changed the title
|
@sildraug Can you please merge this PR? |
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.
Since the $rule may now be array as well as a Closure, the array type must be checked before trying to access indexes.
Also,
applyFiltercalls is corrected to respect it's signature.This should fix
ErrorException Illegal string offset 'name'being thrown.Fixes #48
This change is