Throw an ErrorResponse instead of just an Error for route with no action #7423
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.
Before the React Router 6.4 integration, when you tried to submit to a route with no
action
, we logged a warning but still made the HTTP request knowing it would fail. We decided to stop making the request when we integrated 6.4, but in doing so we lost the semantic nature of the 405 in theErrorBoundary
.This PR brings back the 405 by throwing an
ErrorResponse
instead of anError