Can't send a thread_ts using RTM sendMessage

• 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.

Hey with the recent threading feature, the docs say you should send the thread_ts through the RTM however you do not allow sending any options through your sendMessage function.

RTMClient.prototype.sendMessage = function sendMessage(text, channelId, optCb) {
  return this.send({
    text: text,
    channel: channelId,
    type: RTM_API_EVENTS.MESSAGE
  }, optCb);
};

I will use the API in the meantime to respond to thread_ts messages however allowing us to send a thread_ts through this function would be ideal.

[aoberoi]

@bastienrobert I’m glad you asked! I overlooked the fact that the API of RTMClient has changed quite a bit since the messages above, specifically the v3.x to v4.x transition. That guidance is no longer valid, so allow me to provide a working example:

// Before: sending a simple text message
rtm
  .sendMessage('Poke', conversationId)
  .then(res => console.log(`Message sent: ${res}`)
  .catch(console.error);

// After: sending a simple text message in a specific thread
rtm
  .addOutgoingEvent(true, 'message', { text: 'Poke', channel: conversationId, thread_ts: parent_ts })
  .then(res => console.log(`Message sent: ${res}`)
  .catch(console.error);

In the above example, parent_ts is the ts of the root message of the thread.

[jasonTheNorris]

Hello @Js41637!

You are correct that sendMessage does not support additional options. sendMessage is intended to be a dead simple wrapper for the most common use case of send.

But there is still hope! You can use send to reply to a thread via the RTM. Porting your current code over to something like this should take care of business:

var RTM_EVENTS = require('@slack/client').RTM_EVENTS;

client.send({
    text:      text,
    channel:   channelId,
    thread_ts: thread_ts,
    type:      RTM_EVENTS.MESSAGE,
});

Give that a try and let us know if you run in to any more issues!