Fixed Undefined Key error in nested relationship #547
Merged
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.
Hello there
When using nested, optional relationships (which might be quite an edge case) there is a small possibility that the library is throwing an error.
It is correctly described in the comment above the problematic line, that
The first model in the array is always the parent
. This can be retrieved in most cases by index0
.BUT, if the previously called filter in Illuminate/Database/Eloquent/Collection.php:227 happens to filter the model with index
0
(which is perfectly possible, as otherwise the filter would be unnecessary), then we have anUndefined array key 0
error.Therefore, I propose to change the given implementation to use
reset()
to get the first model, as this truly returns the first model in the array rather than the model with index 0.