Boundary of directives in case of chained resolvers(using custom models) #2072
Unanswered
VirajSirkeck
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What happened?
We are using a directive for a mutation whose one of the fields of the return type is handled by a chained query resolver (to prevent fetching child objects that might not be used). The end of the directive is reached when the main mutation resolver gets resolved and not when all the chained resolvers get resolved.
What did you expect?
Is there a way to increase the boundary of the directive so that the end of the directive is reached when the complete api is complete i.e. the end of the directive is reached when the last resolver is resolved?
Minimal graphql.schema and models to reproduce
graphql.schema:
Custom model:
versions
go run github.com/99designs/gqlgen version
? v0.14.0-devgo version
? 1.17.8 darwin/arm64Beta Was this translation helpful? Give feedback.
All reactions