RocketChat / RocketChat/Rocket.Chat
Message Attachment msg_in_chat_window boolean acting wierd
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
While developing an app through rocket chat app engine framework when we try to add a button attachment with msg_in_chat_window boolean , When the boolean is true the message sent by the user through the app should be shown in chat window and when boolean is false the message should not be shown in the chat but should be sent .
Steps to reproduce:
- Add an attachment of type button with some text and msg attribute to the message using rocket chat app
- Clicking on the button should result in the button clicking user to send the msg attribute value message to chat
- The message should be sent

The attachment object
Expected behavior:

Actual behavior:
The Button gets hidden instead of the msg to be sent and also when the boolean is true the message is hidden which is to be sent

Server Setup Information:
- Version of Rocket.Chat Server:
- Operating System:
- Deployment Method:
- Number of Running Instances:
- DB Replicaset Oplog:
- NodeJS Version:
- MongoDB Version:
Client Setup Information
- Desktop App or Browser Version:
- Operating System:
Additional context
Relevant logs:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the button attachment behavior in the Rocket.Chat App Engine with msg_in_chat_window set to true and false. Compare whether the message is sent and whether it appears in the chat window; done means both visibility cases match the described expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100