[7.x] Fix serialization of models when sending notifications #32051
Conversation
This file contains 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.
Fixes #32039, caused by a previous pull request of mine (#31675).
Wrapping models in a normal collection causes them to no longer be properly serialized as the normal collection does not implement
Illuminate\Contracts\Queue\QueueableCollection. So Models are now wrapped in an eloquent collection instead.I also added an extra check to prevent the job from wrapping the notifiable(s) if it receives a collection (rather than a object or an array), this makes sure any custom queueable collections aren't re-wrapped (breaking their serialization logic)