Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve custom resolvers boilerplate #347

Closed
dsandip opened this issue Sep 2, 2018 · 1 comment
Closed

Improve custom resolvers boilerplate #347

dsandip opened this issue Sep 2, 2018 · 1 comment
Assignees

Comments

@dsandip
Copy link
Member

dsandip commented Sep 2, 2018

WIP: https://github.com/praveenweb/graphql-custom-resolver-example

Location: https://github.com/hasura/graphql-schema-stitching-demo

@shahidhk
Copy link
Member

shahidhk commented Sep 3, 2018

@dsandip Can't we move this to the docs repo?

@shahidhk shahidhk closed this as completed Sep 6, 2018
shahidhk added a commit to shahidhk/graphql-engine that referenced this issue Sep 11, 2018
hasura-bot pushed a commit that referenced this issue Mar 13, 2024
V3_GIT_ORIGIN_REV_ID: 805e0d008954617e85ad6e1688f8016a85748bb5
hasura-bot pushed a commit that referenced this issue Mar 19, 2024
## Description

Following on from #347, this PR separates "query requests" and "mutation
requests" at the level of the query plan, rather than the individual
fields. The result of this is that we can separate the functions to plan
and execute the two things entirely, which will make it easier in the
forthcoming PR to add support for transactions.

There's almost certainly some further refactoring that could be done
here, but I'm choosing to wait until transactions are in place before
getting too excited.

V3_GIT_ORIGIN_REV_ID: 849f4682cc01d3b9e44d2748e4cc34382c8547a7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants