docs: improve dynamic routes examples #87985
Open
+3
−3
Conversation
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
This change clarifies the behavioral difference between catch-all ([...slug]) and optional catch-all ([[...slug]]) routes by making the zero-segment case explicit. This helps readers understand when to use each pattern without introducing overlapping route examples.
Collaborator
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
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.
What?
Clarifies the behavioral difference between catch-all (
[...slug]) and optional catch-all ([[...slug]]) routes in the Dynamic Routes documentation.Why?
Readers may not clearly understand the distinction between these two patterns because the original examples use different base paths. This change makes the zero-segment case explicit, helping developers choose the correct pattern for their use case.
How?
Adds a short explanation highlighting that catch-all routes require at least one segment, while optional catch-all routes allow zero or more segments, without introducing overlapping route examples.