You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Idea: change the current endpoint to accept a query that switches the internal logic to use the Meteor method of sendMessage. The reason we can't change the current logic is because it allows sending the same message to multiple channels thus resulting in more than one message object which is also the reason we can't allow the _id to be provided since then it wouldn't be unique on that index.
Description:
We currently have a chat.postMessage API:
https://rocket.chat/docs/developer-guides/rest-api/chat/postmessage (outdated)
But that doesn't allow us to specify an id for the message like the Real-Time API:
We need something similar, but REST.
Either a new one (chat.sendMessage) mimicking the Real-Time API,
or adding _id in the existing chat.postMessage
The text was updated successfully, but these errors were encountered: