-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[graphql] support async resolvers #14915
Conversation
Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
18690a8
to
7a4e83d
Compare
Deploy preview for dagit-storybook ready! ✅ Preview Built with commit 7a4e83d. |
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit b58ce55. |
Found this in my pr queue stale from last time this got asked about in the summer. Theres no planned uses of this that im aware of but wanted to blow the dust off and get the tests passing. |
7a4e83d
to
b58ce55
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's pretty cool that this works.
changes how the root graphql execution is invoked to support
async
resolvers, unlocking the ability to use something like DataLoader https://docs.graphene-python.org/en/latest/execution/dataloader/ to effectively batch request instead of issuing them serially.How I Tested These Changes
added test
did some quick py-spy profiling to make sure nothing stood out