refactor(theme): Sidebar isActive algorithm should be same with Route match
#1863
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.

Summary
We currently have two matching algorithms for sidebar
1.
matchPath(sidebarKey, pathname)ingetSidebarGroupData(pathname: string)decide which sidebarGroup would show, and it will calculate with these keys
'/','/guide'one by onerspress/packages/theme-default/src/logic/getSidebarDataGroup.ts
Lines 22 to 42 in fb81b99
2.
match(sidebarGroup, pathname)decide which sidebarItem is active,
to match
item.linkrecursivelysome code changes
pathname -> routePathlogic topathnameToRouteServiceit is a core function which bridge
RouteandSidebarpathnameToRouteServiceto decide which sidebar is activeBefore, we wrote the algorithm repeatedly
This
pathnameToRouteServiceshould be the above algorithm 2, it comes fromsreact-router-domand already have been used in RouteOf course, Sidebar
isActiveshould use the same logic with Routeapi-extractorgenerated pathfor rspeedy
Related Issue
Checklist