-
-
Notifications
You must be signed in to change notification settings - Fork 749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add @defer support to the execution engine. #59
Comments
This would seriously blow people's minds. |
This is coming in April |
Dont tease me! April 1st? 😉 |
We are aiming at April 14 or the week after that. |
So, after talking to people on the relay channel I have changed my perspective on this one.... the Apollo way for @defer seemed so messy. But talking to guys on the relay channel it seems that relay will go a different way and instead will provide @defer on fragments rather than fields. This makes much more sense and allows for much more powerful ways to delay fields. Moreover, with this we would not be forced to make a field nullable in order to be able to defer it. |
en_js [1 day ago] Our current approach is that @defer can be used with inline fragments or fragment spreads while @stream can be used on plural fields. We don't have a publicly available version of a spec because, as noted, we aren't ready to proceed with an RFC yet. If you're curious you can look at the defer/stream-related tests and transforms, but again, just beware that they're subject to change. |
Facebook will start moving this into the spec. |
hello any update on @defer? is it going to be in version 11.0.0? |
Still not spec'ed |
This one is now merged and released |
https://www.apollographql.com/docs/react/features/defer-support.html
https://blog.apollographql.com/new-features-in-graphql-batch-defer-stream-live-and-subscribe-7585d0c28b07
https://www.reddit.com/r/graphql/comments/8wv1da/status_on_graphql_batch_stream_defer_live_etc/
facebook/relay#288
facebook/relay#2554
facebook/relay#2194
https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream
System.Net.Http.MultipartContent
The text was updated successfully, but these errors were encountered: