Description

The callback registration pattern is a powerful way to decouple the concerns of handling slack interactive-message callbacks, separating request parsing and validation logic common to all slack app callbacks from the business logic of handling and responding to those callbacks.

One thing I struggled with when moving from handling the raw requests myself to using the @slack/interactive-messages@1.4.0 package was losing access to the raw request or underlying payload. Once I had a handler matching I could see the payload inside my handler to learn how to better handle that type of payload. When I didn't have any matching handler, however, I couldn't understand why my matchers were failing to match.

In these cases when no handler is found it would be very useful to expose the raw payload in the interactive-messages adapter debug logs.

This could be as simple as adding the following:

debug({ payload })

to the adapter.dispatch(...) method just after logging that "dispatch could not find a handler"

What type of issue is this? (place an x in one of the [ ])

• bug
• enhancement (feature request)
• question
• documentation related
• testing related
• discussion

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Packages:

Select all that apply:

• @slack/web-api
• @slack/events-api
• @slack/interactive-messages
• @slack/rtm-api
• @slack/webhooks
• I don't know

Reproducible in:

package version:

• @slack/interactive-messages@1.4.0

node version:

• v10.16.0

OS version(s):

• macOS Catalina 10.15.1

Steps to reproduce:

1. register a callback with constraints that do not match the callback (e.g. misspell the callback_id value)
2. enable debug logging in your app
3. initiate the callback from slack
4. see the dispatch could not find a handler message in the logs

Expected result:

See the raw { payload } object in the logs so that I can learn what slack sends and compare it to my registered matchers to understand why none of my handlers matched.

Actual result:

Cannot see the inputs (the payload) so cannot understand why my configured callback handlers didn't match and fire.