7051d25519
When revalidating a page that corresponds with a dynamic path and when using the “type” parameter, eg `revalidatePath(“/dynamic/1”, “page”)` corresponding with `/dynamic/[id]`, the wrong cache tags would be checked to determine if a revalidation occurred. This is because the “derived” cache tags created for a `/dynamic/[id]/page` are: - /dynamic/[id]/layout - /dynamic/[id]/page Additionally, a tag is added for the current canonical URL, so the final tag would be: - /dynamic/1 Thus a fetch on `/dynamic/1` would be tagged with the following: - /layout - /dynamic/layout - /dynamic/[id]/layout - /dynamic/[id]/page - /dynamic/1 Calling `revalidatePath(“/dynamic/1”, “page”)` would signal to revalidate caches tagged `/dynamic/1/page` in the current logic. However, this tag doesn’t exist given the above, so it would be a no-op and wouldn't properly re-invoke the fetch. This updates the docs to explicitly call out that if you are attempting to revalidate a path that corresponds with a dynamic page, that you should not provide a "type" argument. Fixes #62071 Closes NEXT-3302 |
||
---|---|---|
.. | ||
create-next-app | ||
eslint-config-next | ||
eslint-plugin-next | ||
font | ||
next | ||
next-bundle-analyzer | ||
next-codemod | ||
next-env | ||
next-mdx | ||
next-plugin-storybook | ||
next-polyfill-module | ||
next-polyfill-nomodule | ||
next-swc | ||
react-refresh-utils | ||
third-parties |