-
Notifications
You must be signed in to change notification settings - Fork 651
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
Document hasNext: False response case #4373
Comments
I added a paragraph in 56cc68a. Let me know what you think |
@martinbonnin This looks great thanks! |
martinbonnin
pushed a commit
that referenced
this issue
Sep 8, 2022
Co-authored-by: Martin Bonnin <[email protected]> add a link to the (upcoming) documentation update date Update docs/source/fetching/defer.mdx Co-authored-by: JV <[email protected]> Update CHANGELOG.md Co-authored-by: JV <[email protected]> Update CHANGELOG.md Co-authored-by: JV <[email protected]> Update docs/source/fetching/defer.mdx Co-authored-by: JV <[email protected]> trying to make yaml happy update `@defer` to stage 2 draft and mention empty `hasNext: false` payloads see #4373 updates from apollographql/apollo-client#10079 fix an instance of Client -> Kotlin
martinbonnin
added a commit
that referenced
this issue
Sep 8, 2022
* Prepare changelog and doc for next version Co-authored-by: Martin Bonnin <[email protected]> add a link to the (upcoming) documentation update date Update docs/source/fetching/defer.mdx Co-authored-by: JV <[email protected]> Update CHANGELOG.md Co-authored-by: JV <[email protected]> Update CHANGELOG.md Co-authored-by: JV <[email protected]> Update docs/source/fetching/defer.mdx Co-authored-by: JV <[email protected]> trying to make yaml happy update `@defer` to stage 2 draft and mention empty `hasNext: false` payloads see #4373 updates from apollographql/apollo-client#10079 fix an instance of Client -> Kotlin * revert changes to the tests * update CHANGELOG.md Co-authored-by: Martin Bonnin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Relates to apollographql/router#1687
I think it's fine to release as-is and let users debounce for now. Functionality is still there. It's just sub-optimal. Users can still call
.watch()
, they just get an extra event in the initial Flow.Though we should document how handle this case in our preliminary
@defer
documentationThe text was updated successfully, but these errors were encountered: