Unverified Commit 2932b932 authored by Pavan Shinde's avatar Pavan Shinde Committed by GitHub

docs: fix ISR guide link to res.revalidate (#89342)

<!--
Thanks for opening a PR! Your contribution is much appreciated. To make
sure your PR is handled as smoothly as possible we request that you
follow the checklist sections below.

Choose the right checklist for the change(s) that you're making:

For Contributors

Improving Documentation

• [x] Run pnpm prettier-fix to fix formatting issues before opening the
PR.
• [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
Fixing a bug

• [ ] Related issues linked using fixes #number
• [ ] Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
• [ ] Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
Adding a feature

• [ ] Implements an existing feature request or RFC. Make sure the
feature request has been accepted for implementation before opening a
PR. (A discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
• [ ] Related issues/discussions are linked using fixes #number
• [ ] e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
• [ ] Documentation added
• [ ] Telemetry added. In case of a feature if it's used or not.
• [ ] Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
For Maintainers

• [ ] Minimal description (aim for explaining to someone not on the team
to understand the PR)
• [ ] When linking to a Slack thread, you might want to share details of
the conclusion
• [ ] Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
• [ ] Add review comments if necessary to explain to the reviewer the
logic behind a change
What?

Fix a broken link in the ISR guide by switching to a site-absolute
/docs/... URL for the res.revalidate reference.

Why?

Without the leading /, the link can resolve as a relative path and break
depending on where it’s rendered.

How?

Update the ISR guide link target to a site-absolute
/docs/pages/guides/incremental-static-regeneration#on-demand-validation-with-resrevalidate.

Closes NEXT-
Fixes #
-->
parent 2521b8ad
...@@ -285,7 +285,7 @@ For a more precise method of revalidation, invalidate cached pages on-demand wit ...@@ -285,7 +285,7 @@ For a more precise method of revalidation, invalidate cached pages on-demand wit
For example, this Server Action would get called after adding a new post. Regardless of how you retrieve your data in your Server Component, either using `fetch` or connecting to a database, this will invalidate the cache for the entire route. The next request to that route will trigger regeneration and serve fresh data, which will then be cached for subsequent requests. For example, this Server Action would get called after adding a new post. Regardless of how you retrieve your data in your Server Component, either using `fetch` or connecting to a database, this will invalidate the cache for the entire route. The next request to that route will trigger regeneration and serve fresh data, which will then be cached for subsequent requests.
> **Note:** `revalidatePath` invalidates the cache entries but regeneration happens on the next request. If you want to eagerly regenerate the cache entry immediately instead of waiting for the next request, you can use the Pages router [`res.revalidate`](docs/pages/guides/incremental-static-regeneration#on-demand-validation-with-resrevalidate) method. We're working on adding new methods to provide eager regeneration capabilities for the App Router. > **Note:** `revalidatePath` invalidates the cache entries but regeneration happens on the next request. If you want to eagerly regenerate the cache entry immediately instead of waiting for the next request, you can use the Pages router [`res.revalidate`](/docs/pages/guides/incremental-static-regeneration#on-demand-validation-with-resrevalidate) method. We're working on adding new methods to provide eager regeneration capabilities for the App Router.
```ts filename="app/actions.ts" switcher ```ts filename="app/actions.ts" switcher
'use server' 'use server'
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment