Skip to content
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

Please update the @defer blog post #2700

Closed
dandv opened this issue May 19, 2019 · 1 comment
Closed

Please update the @defer blog post #2700

dandv opened this issue May 19, 2019 · 1 comment

Comments

@dandv
Copy link
Contributor

dandv commented May 19, 2019

Not sure where to file this to get the appropriate attention:[1]

The Introducing @defer blog post got my colleague all excited about the feature, only to waste a good amount of time figuring out it was actually removed and on the roadmap for 3.0.

Please add a status notice at the top of that blog post.

[1]: Comments left to this end on the post itself did not get attention

@abernix
Copy link
Member

abernix commented May 27, 2019

Thank you very much for opening this, @dandv, and apologies to your colleague for the time they had to expel while digging into this. I had some changes made to the blog post, including what I hope is a very clear warning that it's experimental and not production ready (and not in any current release!), which will hopefully save future readers.

We are still planning the re-introduction of @defer, but it's dependent on some other architectural changes to both the client and the server, in order to make sure that @defer can be supported end-to-end by client, server, tooling, Apollo Engine, etc.

@abernix abernix closed this as completed May 27, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants