**What** Currently, when setting a `belongsTo` relationship on the DML with the otherside being `hasMany` it result in a wrongly generated gql output making the belongs to being a collection of the relation instead of the relation directly. This pr fixes this issue
118 B
118 B
@medusajs/utils
| @medusajs/utils |
|---|
| patch |
fix(utils/dml): set-relationship graphql generator from DML wrong managed belongsTo