Return the object property that is actually accessible. #3371
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 there is a check for two types of property, we should also return the one we found.
Without this, cases where a property is accessed that exists in the cast of the object, but not directly, will not be available and will throw notices and end up with NULL.
We noticed this in our project because of using a DateTimeInterface's date property (which I wouldn't recommend, but still). The if check will respond
true
because if you cast a DateTimeImmutable to an array it has a 'date' key, but trying to access it directly does not actually work (at least not in PHP 7.4. It apparently worked before as the code had been running fine before we upgraded.)My proposed change should work in all situations.