-
-
Notifications
You must be signed in to change notification settings - Fork 606
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
Support FetchPolicy.cacheFirst on Query widget #366
Comments
Yea, that line does look unnecessary, not sure why it is there. When the policy is |
Yes, that's the same as I thought. Maybe @HofmannZ could shed some light on the problem as this commit was his :) |
@lucasavila00 can you PR this? |
@mainawycliffe I've raised a PR with the changes. |
🎉 This issue has been resolved in version 2.1.1-beta.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.0.0-beta.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
I'm trying to use the Query widget to query something only if it is not cached but I can't.
If I set the Fetch Policy to cacheFirst I'd like it to be the fetch policy, but since the Query widget replaces the fetch policy to cacheAndNetwork I can't do this.
I don't know why the widget does this but a fix would be to simply remove the code that replaces the fetchPolicy.
The text was updated successfully, but these errors were encountered: