Unexpected behaviour when upgrading to mongoose 6 with mutation resolvers

[trollcus]

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.

[steverogers180]

Send the whole document with an updated field. That's the only solution for now until someone fixes this.