fix(Apollo): Set initialFetchPolicy to 'cache-first' and implement a basic nextFetchPolicy #870
+36
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The nextFetchPolicy is taken from the Apollo documentation
Context
We saw that when navigating between pages using links the Apollo cache was not used to render the data even though it was pre-populated by the SSR of the app. This was caused by the
cache-and-network
setting that always fires a request to the server to ensure to have the freshest data possible. It's not relevant for the initial load since we can be certain it is fresh.cache-and-network