feat: add "unhandledException" event #566
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.
Changes
Adds a new event to the HTTP events map called
unhandledException
. If the listener for that event is provided, whenever an unhandled exception occurs in therequest
listener, theunhandledException
listener will be called (if present).This allows the client to opt-out from the default handling of exceptions (producing 500 error responses), as well as do so conditionally. If the
unhandledException
listener does nothing, the default handling kicks in.Note: The
unhandledException
listener receives a readonlyrequest
instance (non-interactive request). To affect the request, it receives an additionalcontroller
object with methods.respondWith()
and.errorWith()
.