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
Hi! I'm trying to use GraphiQL with @defer. I found that it has some support built in via enableIncrementalDelivery, which defaults to true.
However, there's a long-running proposal to change the standard response structure: graphql/graphql-spec#742 .In that proposal, each patch would include a { incremental: [ ... ] } array which includes { data: ... , path: ... } entries.
our implementation should be updated with whatever the language spec you linked to, and in addition, whatever the graphql over http spec supports! please feel free to open a PR if you like!
Hi! I'm trying to use GraphiQL with
@defer
. I found that it has some support built in viaenableIncrementalDelivery
, which defaults totrue
.However, there's a long-running proposal to change the standard response structure: graphql/graphql-spec#742 .In that proposal, each patch would include a
{ incremental: [ ... ] }
array which includes{ data: ... , path: ... }
entries.Although it's only a proposal, it was implemented in GraphQL-JS about a year ago (graphql/graphql-js#3659) and has also been added to urql and apollo client
It looks like GraphiQL expects
data
andpath
to be top-level keys in the server's response:graphiql/packages/graphiql-react/src/execution.tsx
Lines 218 to 219 in 7daa163
What do you think about also checking for
incremental: ...
entries there, to support this new response format?Thanks!
The text was updated successfully, but these errors were encountered: