Calling respond() with a simple string does not work

[aoberoi]

Description

Even through respond() is typed to accept a string argument, it will not post the body in the correct format for a simple message to be accepted by the platform. We may need to adjust the ExpressReceiver implementation to wrap the simple string in a JSON body with a text property.

As this is implemented, it might make sense to extract some sort of Receiver utilities file, which can assist with generating more Receiver implementations, which have more consistent behavior amongst them. This is an alternative to having a common base class which all implementations extend, and the base class provides this functionality.

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.

Reproducible in:

package version: all

node version: all

OS version(s): all

Steps to reproduce:

1. Recieve a slash command
2. Within the listener, try calling respond('test');
3. Observe that the message is not sent in the channel, and an error is reported on the console.

Expected result:

Message posted in Slack

Actual result:

Nothing.

[SpencerKaiser]

I have the exact same issue and it's a total blocker for me using Bolt because I need to post ephemeral messages.

[SpencerKaiser]

@aoberoi I found a workaround! The importance of token isn't really clear in the docs, but if you pass token into respond, it succeeds. Here's an example:

app.command('/wat', async ({ ack, context, respond }) => {
    ack();
    respond({
      token: context.token,
      text: 'wat'
    });
});

[seratch]

This issue has been fixed by #379