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
When an instance is being created, all its relations defined in the belongsTo attribute are handled before the instance is created.
To handle that, the related instance is created and its id is stored. The result with this approach is the reuse of the related instance.
For example, if a Post belongs to a User and you create 5 instances with the PostBuilder, it first create one user and then assign it to all the 5 posts... and this is the desired behaviour, unless the relation must be unique.
For example, if a user must have one (and only one) account, the AccountBuilder must create one user for each account being created
The text was updated successfully, but these errors were encountered:
When an instance is being created, all its relations defined in the belongsTo attribute are handled before the instance is created.
To handle that, the related instance is created and its id is stored. The result with this approach is the reuse of the related instance.
For example, if a Post belongs to a User and you create 5 instances with the PostBuilder, it first create one user and then assign it to all the 5 posts... and this is the desired behaviour, unless the relation must be unique.
For example, if a user must have one (and only one) account, the AccountBuilder must create one user for each account being created
The text was updated successfully, but these errors were encountered: