fix(registry): Prioritize route registration based on specificity #18002
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.
Involved Issue / 该 PR 相关 Issue
Close #
Example for the Proposed Route(s) / 路由地址示例
New RSS Route Checklist / 新 RSS 路由检查表
Puppeteer
Note / 说明
A
sortRoutes
function has been introduced to prioritize route registration based on segment type and order. Literal segments are prioritized over parameter segments, ensuring that more specific routes are registered first.For instance, with the routes
/xxx/news/:channel
and/xxx/:category
, a request to/xxx/news/sports
will now correctly match/xxx/news/:channel
, while a request to/xxx/products
will match/xxx/:category
.