[5.5] Add support for additional values in relationship firstOrCreate and firstOrNew #18878
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
…hasOneOrMany and MorphOneOrMany relationships
mickeyschwab
changed the title
tillkruss
changed the title
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.
Builder firstOrCreate and firstOrNew accepts a $values parameter to immediately merge in default values when returning a new model. This PR adds the same functionality to hasOneOrMany and MorphOneOrMany relationships.
I wasn't sure what to do regarding the signature change on belongsToMany (firstOrCreate(array $attributes, array $joining = [], $touch = true)) so I've held off for now but am happy to make the same changes for that relationship.