fix(docs): align component order in navigation and lists - #2859
Open
Lisa18289 wants to merge 2 commits into
Open
fix(docs): align component order in navigation and lists#2859Lisa18289 wants to merge 2 commits into
Lisa18289 wants to merge 2 commits into
Conversation
The component navigation took its order from the filesystem, where whole paths are compared and `-` sorts before `/`: `actions/action-group/` came before `actions/action/`. The overview lists sort by the rendered name, so the two views disagreed — also for AvatarStack/Avatar, MessageThread/Message and FormRootError/Form. Both now sort by the rendered label through a shared comparator. In the navigation it is opt-in, because Get Started, Foundations and Patterns order themselves via numeric path prefixes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Lisa18289
requested review from
Jan-Eimertenbrink,
ins0,
maaaathis and
mfal
as code owners
August 19, 2026 13:07
Contributor
Coverage Report for ./packages/components/
File CoverageNo changed files found. |
Replaces the opt-in `sortByLabel` prop with one rule for all sections: a numeric path prefix (`01-design`) decides the order where present, the rendered label otherwise. Get Started, Foundations and Patterns keep their current order — their unprefixed pages already sort identically by label. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
🚀 Preview DeploymentPreview environments are ready:
Images:
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The component navigation took its order from the filesystem, where whole paths are compared and
-sorts before/:actions/action-group/came beforeactions/action/. The overview lists sort by the rendered name, so navigation and list disagreed — same for AvatarStack/Avatar, MessageThread/Message and FormRootError/Form.Both now sort by the rendered label through a shared comparator (
compareLabels). Where a path segment carries a numeric prefix (01-design), that prefix keeps deciding the order, so Get Started, Foundations and Patterns stay as authored — their unprefixed pages already sort identically by label. "Deprecated last" stays the primary key in the navigation.Verified in the docs dev server: navigation and list match group by group, and all four sections keep their intended order.
🤖 Generated with Claude Code