Incremental Delivery - Payload Type for Resolvers Returning AsyncIterables

[yaacovCR]

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.

Note: I restarted this poll, as I think the question wording was off.

For resolvers that return async iterables, what should the async iterable yield?

Next Available Value

Next Set of Available Values

Other

For Other, please add your comments to the discussion linked above!

[yaacovCR]

ack-- i restarted the above poll, as I took another look, and saw all the "others", and realized that the question wording was off.

please still feel free to respond with other, and please feel free to add feedback to the discussion linked above no matter how you vote.

[yaacovCR]

Hello all — thanks again for participating in the above poll. 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, I would love to set something up prior to next wg so that the options could be best presented and resolved at that meeting.

[yaacovCR]

Thanks again to all who voted! Please add your feedback as well to the linked discussion above. @graphql/tsc @graphql/implementers @graphql/wg-core

[yaacovCR]

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