change in error handling policy #29
Comments
TomokiMiyauci
added a commit
that referenced
this issue
Oct 8, 2022
`URLRouter` will not grip the error and will try to reslow it as is BREAKING CHANGE: `URLRouter` will not grip the error and throw error as is #29
TomokiMiyauci
added a commit
that referenced
this issue
Oct 8, 2022
stop catching handler errors BREAKING CHANGE: remove `onError` field from router #29
TomokiMiyauci
added a commit
that referenced
this issue
Oct 8, 2022
no export `validateURLRoutes` from API BREAKING CHANGE: no export `validateURLRoutes` close #29
TomokiMiyauci
pushed a commit
that referenced
this issue
Oct 8, 2022
# [3.0.0-beta.1](2.1.0...3.0.0-beta.1) (2022-10-08) ### Features * **routers:** add throwing error to URLRouter ([f8032e8](f8032e8)), closes [#29](#29) * **routers:** remove `onError` field from types ([1870d07](1870d07)), closes [#29](#29) * **utils:** remove `validateURLRoutes` ([4ebbb75](4ebbb75)), closes [#29](#29) ### BREAKING CHANGES * **utils:** no export `validateURLRoutes` * **routers:** remove `onError` field from router * **routers:** `URLRouter` will not grip the error and throw error as is
|
🎉 This issue has been resolved in version 3.0.0-beta.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Stop griping about errors.
Also, if a handler throws an error, it will throw the error as is instead of returning a
500error response.The text was updated successfully, but these errors were encountered: