[9.x] Fire event before route matched #41765
Merged
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
timroberson
changed the title
|
Hey, @timroberson I don't get your idea, we can achieve the same using middleware so what is the point to raise this event. I just wanted to understand the reason why you added this. Thanks |
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.
Fire a new RouteMatching event before the router attempts to find a matching route. This event is a companion to the existing RouteMatched event and allows a developer access to work with the request immediately before and after routing. Since this is simply adding a new event that existing applications will not be subscribed to, I believe it is fully backward compatible. Thank you for your consideration.