Skip to content
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.

Sign up for GitHub

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

Jump to bottom

docs: correcting link to useSearchParams ref #56169

Merged
merged 2 commits into from Sep 28, 2023
Merged

docs: correcting link to useSearchParams ref #56169

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c9f98cc
corrected link to useSearchParams ref
boylett Sep 28, 2023
11264ed
Merge branch 'canary' into patch-2
styfle Sep 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/02-app/02-api-reference/02-file-conventions/layout.mdx
View file
Open in desktop
Expand Up @@ -116,7 +116,7 @@ This performance optimization allows navigation between pages that share a layou

Because `dashboard/layout.tsx` doesn't re-render, the `searchParams` prop in the layout Server Component might become **stale** after navigation.

- Instead, use the Page [`searchParams`](/docs/app/api-reference/file-conventions/page) prop or the [`useSearchParams`](/docs/app/api-reference/functions/use-params) hook in a Client Component, which is re-rendered on the client with the latest `searchParams`.
- Instead, use the Page [`searchParams`](/docs/app/api-reference/file-conventions/page#searchparams-optional) prop or the [`useSearchParams`](/docs/app/api-reference/functions/use-search-params) hook in a Client Component, which is re-rendered on the client with the latest `searchParams`.

### Root Layouts

Expand Down