Drop support for flask 0.x and register default error handler only for HTTPException #12
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.
Since Flask 1.0, it is now possible to register a error handler for generic
HTTPException
(pallets/flask#941, pallets/flask#2314).Because this is not possible with Flask 0.x, the error handler is registered for all error codes as a workaround, which can mess with other extensions registering error handlers if flask-rest-api is initiated last.
This PR addresses this by only registering the error handler for
HTTPException
and dropping support for Flask 0.x. Now other extensions may register error handlers for specific exceptions or codes.