fix: cache-bust GraphQL requests made with graphQLFetch()
#227
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.
Types of changes
Description
This PR cache-busts GraphQL requests made with
graphQLFetch()
. It does this by including the request'sref
as a URL parameter.The Prismic GraphQL API ignores the
ref
parameter; the API reads the ref from a header namedPrismic-ref
.Without this PR, re-running a query may return a locally cached response, even when after the
ref
changes. This happens because caches typically do not take into account headers when caching requests.Related: prismicio/apollo-link-prismic#39
Checklist:
🕸️