-
Notifications
You must be signed in to change notification settings - Fork 203
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
fix: cache value false to rewrite default cache policy #625
base: improve/async-query
Are you sure you want to change the base?
fix: cache value false to rewrite default cache policy #625
Conversation
I need this too, I was even thinking about allowing to set the Try adding reviewers that are able to merge this. |
Looks like I have no rights to add reviewers here :D All that I can do is ping folks and ask them to check. I am just wondering if this repo is still alive :D @timyourivh As a workaround, you can try to use "5.0.0-alpha.11" for now, which does not apply changes. But to be honest this cache issue is not my biggest problem with this module :) |
Hi guys, we are also dealing with the issue, BUT i think even this PR is not enough. Please see bug ticket: #631 |
@awacode21 GOOD LUCK :D |
Old thread here but what have people done here - regarding a work around. Would love to help but just know enough to be dangerous :( and test. |
I disabled cache all together, check my observation here: Later, due to overhead, we dropped GraphQL in favor of traditional REST API |
The same for me. Unfortunately. |
Now cache: false is not affecting on the query policy. So, if the application has 'cache-first' and you need a query with disabled caching, it is not feasible to achieve. This small fix should allow to do it.