[CLEANUP BUGFIX] fix model and factory lookup #5446
Merged
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.
Resolves #4711
Resolves an issue with
createRecord
failing when being called for a non-existent modelFixes an issue found with
toString
implementation in #5117Example Fail case prior to this PR:
Previously, we had overly complicated the process of looking up a model with a mixture of public and private and public-looking but private methods. This complexity resulted in there being multiple code-paths by which a
ModelClass
could be looked up without amodelName
or in which no factory for theModelClass
would be found but we would still attempt tocreate
an instance from a missing factory.Much of this complexity stemmed from the desire to check whether a
ModelClass
existed. I have strengthened our private_hasModelFor
implementation, and trimmed us down to a single publicmodelFor
hook and a single private_modelFactoryFor
hook to eliminate confusion and prevent these sorts of errors from occurring.Deprecates
_modelForMixin
_modelFor
modelFactoryFor