Update documentation to explain behavior in a Catch-all route#89742
Merged
icyJoseph merged 20 commits intovercel:canaryfrom Feb 12, 2026
Merged
Update documentation to explain behavior in a Catch-all route#89742icyJoseph merged 20 commits intovercel:canaryfrom
icyJoseph merged 20 commits intovercel:canaryfrom
Conversation
Updated useSelectedLayoutSegment docs to explain behavior in a Catch-all route.
Updated useSelectedLayoutSegments to explain behavior in a Catch-all route.
Member
|
Thanks for the PR I do believe this behavior is backed by this e2e:
Where, pathnames like, I think the bulletpoints are a good idea, they should stay, but we need to reinforce this gotcha by adding an entry to the For For |
icyJoseph
reviewed
Feb 10, 2026
docs/01-app/03-api-reference/04-functions/use-selected-layout-segment.mdx
Outdated
Show resolved
Hide resolved
icyJoseph
reviewed
Feb 10, 2026
docs/01-app/03-api-reference/04-functions/use-selected-layout-segments.mdx
Outdated
Show resolved
Hide resolved
…segment.mdx Co-authored-by: Joseph <sephxd1234@gmail.com>
…segments.mdx Co-authored-by: Joseph <sephxd1234@gmail.com>
Added example to returns section
Added example to returns section
Contributor
Author
|
@icyJoseph I've added your suggestions. Thnx for the input! |
docs/01-app/03-api-reference/04-functions/use-selected-layout-segment.mdx
Outdated
Show resolved
Hide resolved
docs/01-app/03-api-reference/04-functions/use-selected-layout-segments.mdx
Outdated
Show resolved
Hide resolved
…segment.mdx Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
…segments.mdx Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
icyJoseph
reviewed
Feb 11, 2026
docs/01-app/03-api-reference/04-functions/use-selected-layout-segment.mdx
Outdated
Show resolved
Hide resolved
icyJoseph
reviewed
Feb 11, 2026
docs/01-app/03-api-reference/04-functions/use-selected-layout-segments.mdx
Outdated
Show resolved
Hide resolved
…segments.mdx Co-authored-by: Joseph <sephxd1234@gmail.com>
…segment.mdx Co-authored-by: Joseph <sephxd1234@gmail.com>
icyJoseph
reviewed
Feb 11, 2026
docs/01-app/03-api-reference/04-functions/use-selected-layout-segments.mdx
Outdated
Show resolved
Hide resolved
icyJoseph
approved these changes
Feb 11, 2026
icyJoseph
added a commit
that referenced
this pull request
Feb 18, 2026
<!-- 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 - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - 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? ### Why? ### How? Closes NEXT- Fixes # --> --------- Co-authored-by: Joseph <sephxd1234@gmail.com> Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
No description provided.