Repository navigation
docs: say which value wins when cacheLife runs more than once - #101005
Open
Vladimir-Pirotskiy wants to merge 1 commit into
Open
Vladimir-Pirotskiy wants to merge 1 commit into
Vladimir-Pirotskiy wants to merge 1 commit into
Conversation
When more than one cacheLife call runs in a cache scope, including after an await, each of stale, revalidate and expire keeps the shortest value. The note that advises one call per invocation did not say what happens otherwise, so add that to it. <!-- NEXT_JS_LLM -->
github-actions
Bot
added
the
Documentation
This branch has not been deployed
This file contains hidden or 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
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.
The docs didn't say what happens when cacheLife is called more than once. In that case the shortest value is used, so this PR adds that.