Support user-defined error handlers #26
Merged
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 change fixes #24 by allowing users to define a chain of error handlers. Handlers can be used in two ways, shown below:
Users can register a handler for a specific class (or classes) of Exception, or use the basic syntax for a catch-all. Error handlers end up getting chained together with calls to
Failure.check()
to scope handlers to the appropriate Exception types.In a separate PR I intend to cause HTTPExceptions raised during request routing to be passed to the same handler chain, which would allow users to, for example, define custom 404 handlers.