[5.6] Remove null relationships in loadMorph before grouped by class name - #24322
Merged
Conversation
Contributor
|
could you please provide a more thorough description and use case of what this fixes? also, probably needs to go to 5.7 |
tillkruss
suggested changes
May 25, 2018
tillkruss
left a comment
Contributor
There was a problem hiding this comment.
Please use filter() without a callback.
Contributor
Author
|
@tillkruss Thanks for your review. Use filter() without a callback is just much more concise. |
Contributor
Author
|
@browner12 Here is a example: In this case, |
This file contains hidden or 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
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.
Relationship model may be null when using with() to eager load them, which will cause error in loadMorph() because of the usage of get_class().
So, remove null relationships before group them by class name seems reasonable.