graphql-compose / graphql-compose/graphql-compose-mongoose
Unexpected behaviour when upgrading to mongoose 6 with mutation resolvers
Open
- Dominant language
- TypeScript
- Stars
- 706
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.