fix: cache value false to rewrite default cache policy

[Stanislavsonder]

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.

[sneakylenny]

I need this too, I was even thinking about allowing to set the fetchPolicy manually. But I don't know if there's a reason it was decided to turn it into a boolean.

Try adding reviewers that are able to merge this.

[Stanislavsonder]

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
@Diizzayy @danielroe

@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 :)

[awacode21]

Hi guys, we are also dealing with the issue, BUT i think even this PR is not enough. Please see bug ticket: #631

[Stanislavsonder]

@awacode21 GOOD LUCK :D

[jumptrnr]

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.

[sneakylenny]

but what have people done here - regarding a work around.

I disabled cache all together, check my observation here:
#496 (comment)

Later, due to overhead, we dropped GraphQL in favor of traditional REST API

[Stanislavsonder]

Later, due to overhead, we dropped GraphQL in favor of traditional REST API

The same for me. Unfortunately.