-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expanded on error handling docs #1425
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1425 +/- ##
=======================================
Coverage 81.97% 81.97%
=======================================
Files 18 18
Lines 1476 1476
Branches 434 434
=======================================
Hits 1210 1210
Misses 172 172
Partials 94 94 Continue to review full report at Codecov.
|
@filmaj Can you resolve the conflicts? |
@@ -9,9 +9,48 @@ order: 1 | |||
*Note: Since v2, error handling has improved! View the [migration guide for V2](https://slack.dev/bolt/tutorial/migration-v2) to learn about the changes.* | |||
|
|||
If an error occurs in a listener, it’s recommended you handle it directly with a `try`/`catch`. However, there still may be cases where errors slip through the cracks. By default, these errors will be logged to the console. To handle them yourself, you can attach a global error handler to your app with the `app.error(fn)` method. | |||
|
|||
You can also define more focussed and specific error handlers for a variety of error paths directly on the `HTTPReceiver`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will add the corresponding changes to the JP docs later
These docs are related to #1183 and fixes #1187.
Would love some help on the Japanese docs 😄