fix(cache-handler): persist implicit path tags for PAGES entries #227
Open
KajSzy wants to merge 3 commits into
Open
fix(cache-handler): persist implicit path tags for PAGES entries #227KajSzy wants to merge 3 commits into
KajSzy wants to merge 3 commits into
Conversation
revalidatePath invalidates via _N_T_ path tags in Redis; Pages Router HTML cache entries did not store them on set or registerInitialCache.
Add CI workflow, example page test hooks, and specs covering cache hits, revalidatePath, revalidateTag, and tag profiles against a live Redis stack.
Drop Redis service health options, debug cache env, and turbo test:e2e env passthrough. Rename cache-behavior spec to path-revalidation with App/Pages Router describe blocks.
Collaborator
|
For some reason I lost notifications about PRs/Issues in this repo. Sorry for that. I'll review the PR this week 🫡. |
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
2 participants
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.
When working with nextjs project using
nextjs-cache-handlerI've came up with a workflow how to validate implementation and integration with nextjs itself.This PR introduces integration tests github workflow and fix for
revalidatePathnot working with pages router which is rare situation but still should be supported (ie big projects migrating from pages to app router)