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.

Sign up for GitHub

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

Jump to bottom

fetchPolicy/nextFetchPolicy behavior #6843

Closed
Risbot opened this issue Aug 15, 2020 · 2 comments
Closed

fetchPolicy/nextFetchPolicy behavior #6843

Risbot opened this issue Aug 15, 2020 · 2 comments

Comments

@Risbot
Copy link

Risbot commented Aug 15, 2020

Strange behavior with fetchPolicy and nextFetchPolicy.

Now if I using new vesion, I get more strange behaviors with using fetchPolicy and nextFetchPolicy.

I think with version 3.0.0 it was everything more clear, how use fetchPolicy. Now it is for me little bit magic. Can anybody explain how it work detail and how can i get same result like in version 3.0.0?
@JesseZomer
Copy link

There is bit more info here: #6760 (comment)

@hwillson
Copy link
Member

hwillson commented May 5, 2021

It doesn't sound like there is an outstanding issue here, so closing. Thanks!

@hwillson hwillson closed this as completed May 5, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hwillson @JesseZomer @Risbot