Replies: 4 comments
-
Wow, great response number here! Please vote as well on the additional poll about Payload Type for resolvers returning AsyncGenerators. Please feel free to share feedback as to your choice! It might be easier to consolidate the discussion in one repo -- I would suggest at graphql/defer-stream-wg#38 |
Beta Was this translation helpful? Give feedback.
-
Hello all — thanks again for participating in the above polls. Please share your opinions on the discussion linked above so we can all get a sense of the relevant issues. It would be great if we could do some work on this in advance of the next meeting and present thoughts. If anyone is interested in a breakout discussion of the above aspects of incremental delivery, please let me know, I would love to set something up prior to next wg so that the options could be best presented and resolved at that meeting. |
Beta Was this translation helpful? Give feedback.
-
Thanks again to all who voted! Please add your feedback as well to the linked discussion above. @graphql/tsc @graphql/implementers @graphql/wg-core |
Beta Was this translation helpful? Give feedback.
-
Repeating the call — please add your reason for your vote to the linked discussion above. A bit of feedback prior to the next meeting would probably make the next WG discussion on this topic much more impactful. @graphql/tsc @graphql/implementers @graphql/wg-core |
Beta Was this translation helpful? Give feedback.
-
Cross-posting poll from graphql/defer-stream-wg#38 (comment) for greater visibility. Please vote only once for this question from either github repo, as results are linked.
What do you think the payloads yielded by
execute
's AsyncGenerator should consist of?A Single AsyncExecutionResult
All Available AsyncExecutionResults
Note: the format of the second option is up for debate, it could be an array of AsyncExecutionResults or some other type.
Beta Was this translation helpful? Give feedback.
All reactions