The RouteNotFound that is used when the router finds nothing is now public #3326
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.
When no routes match the current request,
DefaultResponder
throws theRouteNotFound
error.This PR makes that error public, allowing any middleware to handle that specific scenario.
Unlike the CatchAll route
**
, a middleware catching theRouteNotFound
works across all HTTP methods automatically.This would be used in a middleware like so: