You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
by default, no operation results are cached unless you set cache hints
since this is a reference/educational project, keeping default behaviours is likely the best way to avoid confusion for beginners
as a side note: the code you linked is client code from the website itself; it does not prescribe the server's caching behaviour. aka: fetchPolicy: "no-cache" is not related to the API response containing the cache-control: no-store header
Testing graphql caching in the downstream and found
cache-control: no-store
header in the response.What was the consideration of not allowing caching for the queries and mutations?
graphqlzero/apps/graphqlzero-web/pages/index.tsx
Lines 581 to 588 in f577a18
The text was updated successfully, but these errors were encountered: