I’m experiencing some weird behaviour when using @custom directives fields in my Dgraph GraphQL schema. I encountered this first on my locally running Dgraph instance inside Docker, but was able to replicate the issue on Slash GraphQL as well. The example I came up to replicate the problem is as f…

Custom field resolvers are not always called

abhimanyusinghgaur (Abhimanyu Singh Gaur) February 10, 2021, 6:50am 6

Hi @cmd-johnson,
This issue has been fixed with following PR: https://github.com/dgraph-io/dgraph/pull/7371 which will be part of the 21.03 release.

Topic		Replies	Views
Creating custom resolvers for Dgraph GraphQL GraphQL kind:question	20	3582	January 22, 2021
Custom DQL resolver for field define in GraphQL schema GraphQL kind:enhancement , status:accepted , ticket:created	5	1610	December 23, 2020
The `@custom` directive - Graphql Documentation	0	493	August 28, 2020
@custom resolver results in status code: 400 GraphQL kind:bug	8	879	October 29, 2020
Overview - Graphql Documentation	0	396	August 28, 2020