-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Support returning async iterables from resolver functions #2757
Conversation
@robrichard Since ATM we are using a very similar algorithm I'm worried that we will also have memory leak: |
f612eb6
to
d25cf40
Compare
f1ddb83
to
10f12a1
Compare
e93482c
to
b393729
Compare
6415aa1
to
93bd84a
Compare
2153dda
to
fa38819
Compare
c2d20a1
to
971ce43
Compare
e8c1a70
to
09d56d6
Compare
09d56d6
to
8c6d731
Compare
The latest changes of this PR are available on NPM as Also you can depend on latest version built from this PR: |
7e793c1
to
4aa22c4
Compare
✅ Deploy Preview for compassionate-pike-271cb3 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
4aa22c4
to
a49dec8
Compare
a49dec8
to
cddf009
Compare
cddf009
to
1a84993
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.
My review (requested by @saihaj ) is basically that we should allow resolvers to return async iterables of iterables, not of individual items. See graphql/defer-stream-wg#38
1a84993
to
6aeb21c
Compare
b742343
to
92ef2af
Compare
92ef2af
to
fd12a27
Compare
ab235c2
to
18a6145
Compare
18a6145
to
58c72ab
Compare
We decided at last js-wg to give this a few days, but it seems to have slipped. It looks good to me. @IvanGoncharov @saihaj ? |
58c72ab
to
dc1d8b4
Compare
Support returning async iterables from resolver functions
dc1d8b4
to
2826e53
Compare
@robrichard Merged, sorry for the long overdue review. |
Co-authored-by: Rob Richard <rob@1stdibs.com>
Continuation of #2712
Depends on #3134