[Routing] Fix documentation on router method option usage #20803
Conversation
This file contains 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
carsonbot
changed the title
|
Santiago, thanks for fixing this ... and I'm sorry for adding this wrong doc. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This update corrects the documentation to reflect the current behavior of the
--methodoption in the router. The previous lines suggesting multiple--methodoptions for displaying routes matching all given methods were incorrect. The system now only considers the last method passed. This fix removes the lines that caused confusion, clarifying that only the last method, such as PATCH, will be consideredAdditionally, if it's considered a good idea, I can implement a new feature to allow multiple methods to be passed and match routes accordingly, enabling more flexibility in route debugging.