data is cached when fetchPolicy is no-cache and notifyOnNetworkStatusChange:true #7611
Assignees
Labels
Comments
2 tasks
benjamn
added a commit
that referenced
this issue
Mar 15, 2021
…cache-fetchpolicy" This reverts commit 319993e, reversing changes made to 6120401. Because #7611 could be a visible change for some applications, we've decided to relocate these changes onto the release-3.4 branch, rather than main, so we revert the PR on main, merge main into release-3.4, then un-revert the PR on the release-3.4 branch.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Intended outcome:
Data should not be cached when fetchPolicy is no-cache, regardless of notifyOnNetworkStatusChange option.
Actual outcome:
Data is cached when fetchPolicy is no-cache and notifyOnNetworkStatusChange:true.
First requested data is not cached as intended, but all requested data by setting variables or refetching is cached.
How to reproduce the issue:
Here is the reproduction link.
If you set variable 1 -> 2 and check console log, you can see data has been cached regardless of
no-cachefetchpolicy.Versions
System:
OS: macOS 11.1
Binaries:
Node: 12.19.0 - /usr/local/bin/node
Yarn: 1.22.5 - ~/.yarn/bin/yarn
npm: 6.14.8 - /usr/local/bin/npm
Browsers:
Chrome: 87.0.4280.141
Safari: 14.0.2
npmPackages:
@apollo/client: ^3.2.4 => 3.2.4
It also happens in the latest version.
The text was updated successfully, but these errors were encountered: