GraphQL @defer and @stream

[Keweiqu]

We’ve been experimenting with @defer and @stream at Facebook for a while now -- Lee first discussed the idea of @defer and @stream in 2016. Over the last three years, we've done a ton of iterations as we uncovered and resolved issues and edge cases following that initial approach. We're now seeing a renewed demand for these ideas in the open source community:
graphql/graphql-js#2318
graphql/graphql-js#2319

Given that Facebook’s increased internal usage makes us more confident in our approach, it seems like a good time to start a discussion of what the next steps would be. Opening this issue with some strategic questions:

• What's the best way to drive @defer and @stream standardization?
• Should these features be part of the official spec or a supplemental specification (e.g. connections)?
• If we decide these features are worthy of standardization, what's the best way of driving towards alignment? Should we set up a stream/defer focused-WG?

[leebyron]

Closing this issue since it's now a recurring agenda item!

[n1ru4l]

Just wanna link this here (as this issue always pops up first in google):

Official Feedback Issue for graphql.js defer & stream