Docs: Clarify routing priority earlier#641
Open
kevinsimper wants to merge 1 commit intohonojs:mainfrom
Open
Conversation
yusukebe
reviewed
Apr 15, 2025
| }) | ||
| ``` | ||
|
|
||
| ## Routing Priority |
Member
There was a problem hiding this comment.
The description is perfect. It's clear!
But I think you should not move this section to the above. The current position below of "Routing with host Header value" is good. This "Routing Priority" is important, but the user should read it after understanding basic routing syntaxes. It's my opinion.
codeOwlAI
pushed a commit
to codeOwlAI/website
that referenced
this pull request
Jun 29, 2025
adopter onboarding for Li Auto
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
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.
Moved the "Routing priority" section up and expanded it to better explain how Hono matches routes based on registration order. This aims to proactively address common confusion where parameterized routes might unintentionally capture requests intended for more specific static routes defined later. Added examples to illustrate the importance of ordering static vs. dynamic paths and also clarified the grouping order example.