Hotchocolate: Add @defer support to the execution engine.

Created on 13 Jun 2018  路  14Comments  路  Source: ChilliCream/hotchocolate

Most helpful comment

This would seriously blow people's minds.

All 14 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.

677

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]
Thanks for the extra context. We're currently experimenting with "native" support for @defer and @stream in our internal GraphQL server and our GraphQL clients (Relay and our native client). As we did with GraphQL itself and our subscriptions RFC/spec we plan to get experience using the approach and validating it at scale before proceeding with any RFC.

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?

This one is now merged and released

Was this page helpful?
0 / 5 - 0 ratings