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
If you have a BelongsToMany association, and you load that association, the data of the through model will be placed on a different key depending on whether it was eager loaded or lazy loaded
When eager loaded, the key is the name of the model
When lazy loaded, the key is the name of one of the associations
To replicate the v6 behavior, the key should always be the name of the model
No, I don't have the time, and I understand that I will need to wait until someone from the community or maintainers is interested in resolving my issue.
Indicate your interest in the resolution of this issue by adding the 👍 reaction. Comments such as "+1" will be removed.
The text was updated successfully, but these errors were encountered:
ephys
added
type: bug
pending-approval
Bug reports that have not been verified yet, or feature requests that have not been accepted yet
and removed
pending-approval
Bug reports that have not been verified yet, or feature requests that have not been accepted yet
labels
Mar 25, 2024
Issue Creation Checklist
Bug Description
If you have a
BelongsToMany
association, and you load that association, the data of the through model will be placed on a different key depending on whether it was eager loaded or lazy loadedWhen eager loaded, the key is the name of the model
When lazy loaded, the key is the name of one of the associations
To replicate the v6 behavior, the key should always be the name of the model
Reproducible Example
Here is the link to the SSCCE for this issue: sequelize/sequelize-sscce#275
Environment
Would you be willing to resolve this issue by submitting a Pull Request?
Indicate your interest in the resolution of this issue by adding the 👍 reaction. Comments such as "+1" will be removed.
The text was updated successfully, but these errors were encountered: