You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Still in the early stages but thought it would be worth getting this on your radar.
From reading the spec, it looks like the idea is that @defer and @stream directives could allow for incremental resolution of GraphQL queries (i.e. cascading async resolvers could have their responses returned at a later date).
In the case of the server side, the current protocol should work just fine - the only difference being a query or mutation invocation isn't guaranteed to receive a single next message
Story
Still in the early stages but thought it would be worth getting this on your radar.
From reading the spec, it looks like the idea is that
@defer
and@stream
directives could allow for incremental resolution of GraphQL queries (i.e. cascading async resolvers could have their responses returned at a later date).Server side
In the case of the server side, the current protocol should work just fine - the only difference being a
query
ormutation
invocation isn't guaranteed to receive a singlenext
messageExample query (from blog post)
Example protocol response
Acceptance criteria
@defer
or@stream
The text was updated successfully, but these errors were encountered: