refactor: implement group-based pagination in DocsNavigation #77
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.
Description
This PR refactors the DocsNavigation pagination logic to enable group-based navigation.
Previously, navigation followed the raw order of
config/docs.ts, resulting in an inconsistent sequence across unrelated components.Now, navigation prioritizes movement within the same group, and once a group ends, it automatically continues to the next group.
Changes
group, then proceed to the next or previous group when reaching boundaries.config/docs.ts; it now respects logical grouping.reduce+flatstructure for cleaner and more maintainable iteration.Record<string, DocsNavigationCategory[]>) to remove@ts-ignoreand ensure stable autocomplete.Motivation
To eliminate inconsistent navigation caused by the arbitrary order of
config/docs.tsand align pagination with the actual component grouping.This makes the browsing experience more structured — allowing users to explore related components together before moving on to the next group.