graphql-compose / graphql-compose/graphql-compose-mongoose

Setting `false` on a resolver arg in typeConverterResolversOpts doesn't disable it

Open
#15 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
706
Forks
98
PR merge metrics
No merged PRs in 30d

Description

With the code:

```js
const composeWithMongoose = require('graphql-compose-mongoose').composeWithMongoose
const User = require('../../../models/User')

const opts = {
description: 'A user of the application.',
resolvers: {
findMany: {
filter: false
}
}
}

module.exports = composeWithMongoose(User, opts)
```

...`filter` argument is still available on the `findMany` resolver. This code should disable it, no? Or am I understanding it wrong?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.