[6.x] Turn the eloquent collection into a base collection if mapWithKeys loses models #35129
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.
Hey guys.
If you
map
over an eloquent collection and return anarray
instead of amodel
you will receive a support collection.But if you use
mapWithKeys
it will lead to errors.If you try to serialize, it will explode in the sky because of this check.
I noticed
map
has a custom implementation on the eloquent collection to I added one formapWithKeys
with the same behavior.I didn't extract the code to check and decide which collection type to return, to keep this PR light.
Also noticed there is a
mapToDictionary
, should we handle this too?Have a nice day
Adrian