[WIP] fix: resolve and unwrap AsyncHasMany
for store.createRecord()
#9402
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 is a WIP. The code works as expected but a cyclical dependency was introduced that needs to be resolved.
Description
In #9396 the prop types expected by
store.createRecord()
were updated to resolveAsyncBelongsTo
to the underlying model.AsyncHasMany
wasn't handled though, so this PR addresses that. To do so theCreateRecordProperties
type util was updated to look forRelatedCollection
s (which are the result ofAwaited
-ing theAsyncHasMany
type) and then the model used in the collection is turned into a plain array of that model type. This allows the following:Previously this would error because
[existingChildModel]
in the model props wasn't of typeRelatedCollection<ChildModel>
.Notes for the release
N/A