For each release of GraphQL.js, we are now publishing an accompanying release containing an experimental implementation of the @defer and @stream directives. We are hoping to get community feedback on these releases before the proposal is accepted into the GraphQL specification.
You can use this experimental release of GraphQL.js by adding the following to your project's package.json file.
"graphql": "experimental-stream-defer"
A similar release of express-graphql will be coming soon.
I am creating this issue as a placeholder for anyone who has tried out these experimental packages to leave feedback. Please let us know if everything is working as expected or if you run into any issues. Any suggestions for improvements are also welcome.
References:
return on iterable when connection closes
graphql-js
express-graphql
express-graphql@0.12.0-experimental-stream-defer.1content-length in payload should not be required, parsers should use boundary instead
graphql-over-http spec
fetch-multipart-graphql
express-graphql
jgcmarins, kadikraman, maraisr, smagch, AugustoCalaca and 6 moredanielrearden, kadikraman, maraisr, STIENLILLY, ashbuilds and 2 moremaraisr, STIENLILLY, ashbuilds, edno, n1ru4l and 2 moremaraisr, STIENLILLY, ashbuilds, edno and n1ru4lbrainkim, bartenra and n1ru4l
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4