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 updating a nested field with a updateOne resolver, all the other field in that same object field becomes null.
let's say we have:
basic_info {
size
email
}
when updating one of the fields, the other ones becomes null.
Had to downgrade to mongoose 5 for now as it's working as expected there.
The text was updated successfully, but these errors were encountered:
trollcus
changed the title
Unexpected behaviour when upgrading to mongoose 6
Unexpected behaviour when upgrading to mongoose 6 with mutation resolvers
Sep 21, 2021
When updating a nested field with a updateOne resolver, all the other field in that same object field becomes null.
let's say we have:
when updating one of the fields, the other ones becomes null.
Had to downgrade to mongoose 5 for now as it's working as expected there.
The text was updated successfully, but these errors were encountered: