You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling the findAll Collection's method with the option full: true should fetch necessary data with parallel requests and then join the collections using the correct order.
At the moment, this is impossibile because multiple RelationshipCollection instances use the same internal array instance, so the order of added items depends on the resolution of the fetch call.
This PR temporarily fixes the joinCollection behavior for RelationshipCollection which causes duplicated entries in the collection.
To do:
Allow multiple RelationshipCollection instances for the same model
Exec multiple pages fetch in parallel
The text was updated successfully, but these errors were encountered:
Calling the
findAll
Collection's method with the optionfull: true
should fetch necessary data with parallel requests and then join the collections using the correct order.At the moment, this is impossibile because multiple
RelationshipCollection
instances use the same internalarray
instance, so the order of added items depends on the resolution of the fetch call.This PR temporarily fixes the
joinCollection
behavior forRelationshipCollection
which causes duplicated entries in the collection.To do:
RelationshipCollection
instances for the same modelThe text was updated successfully, but these errors were encountered: