-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: make revalidateTags
no-op when list of tags is empty
#2727
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
d7b3458
fix: make `revalidateTags` no-op when list of tags is empty
eduardoboucas 04e5451
fix: oops
eduardoboucas 28339a3
test: add integration test for site-wide purge calls
pieh d0a7f47
Merge branch 'main' into fix/noop-empty-revalidate-tags
pieh 782a106
Merge remote-tracking branch 'origin/main' into fix/noop-empty-revali…
pieh f112f29
fix: filter out empty tags
pieh 4a02e34
test: correct afterEach import
pieh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
import { unstable_cache } from 'next/cache' | ||
|
||
export const dynamic = 'force-dynamic' | ||
|
||
const getData = unstable_cache( | ||
async () => { | ||
return { | ||
timestamp: Date.now(), | ||
} | ||
}, | ||
[], | ||
{ | ||
revalidate: 1, | ||
}, | ||
) | ||
|
||
export default async function Page() { | ||
const data = await getData() | ||
|
||
return <pre>{JSON.stringify(data, null, 2)}</pre> | ||
} |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is mocking and advancing the clock here problematic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we use above in plenty of other places that check behaviors related to stale cache items so I just the same method here
I'm not sure if attempting to mock time would work - conceptually it should of course, but not sure it's worth doing that as most time is spent on setting up fixtures rather than running the test itself anyway (at least in this case)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll go ahead and keep this as is in effort to get this fix out and would say moving to mocking time instead of using ~
sleep
is something to consider (across all unit and integration tests and not just this one) - just let's not use this PR for this