Use array_key_exists instead of isset for "_findVariableInContext" #13
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.
A bit of information on this bug.
Say I have a class with a $description property, value being the meta description of a website.
Now I have a form method in a child view class that returns an array with form values. Like
The initial page load would set the description value to that of the meta description (even though the key is set). This is because isset returns false for an array key that has a NULL value.
array_key_exists
solves this problem nicely.