Use Revalidation for Fetch #54
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
At the moment Next.js will cache all the fetch results, which is not what we wanted. We can either add `{ cache: "no-store" }` to completely disable cache or use the revalidate option to reduce API calls.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
JElgar
approved these changes
Oct 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Close #53
This PR try to use auto revalidation (revalidate after maximum 60s), but I need backend developer to help me check whether the automatic revalidation is working (use vercel preview link should work). Try update content in one of the article and then wait for at most 60s, the content should be refreshed. If not, we probably have to use
{ cache: "no-store" }for now, please let me know about this.