-
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
Clarify /slack/events
path requirement.
#1153
Conversation
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.
Thanks for taking the time to make this pull request! I left one comment on the change. Could you check it out if you have a chance?
Co-authored-by: Kazuhiro Sera <seratch@gmail.com>
Thanks @seratch! Done ✅ |
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.
Thank you!
Codecov Report
@@ Coverage Diff @@
## main #1153 +/- ##
=======================================
Coverage 71.71% 71.71%
=======================================
Files 15 15
Lines 1354 1354
Branches 402 402
=======================================
Hits 971 971
Misses 312 312
Partials 71 71 Continue to review full report at Codecov.
|
* Clarify `/slack/events` path requirement. * We may change the log message in the future; generalize the statement Co-authored-by: Kazuhiro Sera <seratch@gmail.com>
* Clarify `/slack/events` path requirement. * We may change the log message in the future; generalize the statement Co-authored-by: Kazuhiro Sera <seratch@gmail.com>
Summary
I was stumped by the
unhandled request was ignored
errors from a new Bolt app.Eventually found an existing issue here, and commented with the solution.
This PR is my attempt to help other folks avoid this frustration with unclear Request URL requirements.
Requirements (place an
x
in each[ ]
)