[9.x] Fix evaluation of factories returned from definition closure #46891
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.
this was originally fixed in #42344 but in #44107 this was changed to support recycling which removed the
getKey
call so if you had a closure returning a factory in the definition in your factory it would cause an sql error with trying to insert the string representation of the resolved model (in second map of this function) into the database because the factory ends up resolved to model instead of the key. This appears to only happen when using a recycled model viarecycle
in my testing which is whengetRandomRecycledModel
returns model.note: #44328 changed the method to support multiple models but remained without
getKey
call.