-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
skip
is not working correctly with nextFetchPolicy
#8895
Comments
I’m currently on my phone in bed (it’s 3AM), but I bet you if you remove the |
Yes, If we remove |
skip
is not working correctly with nextFetchPolicy
@smitpatel1010 Thanks for the confirmation! I updated the title to reflect this detail; I hope you don’t mind. I’m not too sure about how |
Thanks @brainkim. I will also check if I can find any workaround or any relevant info in docs |
Intended outcome:
If the skip is false in useQuery then a new call should go and the cache should update with a new response.
Actual outcome:
If the skip is false in useQuery then a new call is going correct but the cache is not updating with the latest response came.
How to reproduce the issue:
https://codesandbox.io/s/serene-grass-qwy7b?file=/src/index.js
Open this codesandbox and follow below steps.
then check new call is going and received new data but the cache is not updating the value with the latest response.
The text was updated successfully, but these errors were encountered: