RocketChat / RocketChat/Rocket.Chat
Wrong unread counter messages when delete new(unread) message
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Wrong unread counter messages when start use delete message(own message)
Steps to reproduce:
sent 2 new messages and then delete last message(unread) - unread counter, that get with subscription stream-notify-user(subscriptions-changed), not changed and remains equal to 2; Event "subscriptions-changed" doesn't come
Expected behavior:
unread counter decrease
Actual behavior:
unread counter not changed
Server Setup Information:
- Version of Rocket.Chat Server: 3.2.2
Additional context
use rocket chat api for mobile app with socket
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
Reproduce the issue using the Rocket.Chat API with a socket connection: send two new messages, delete the last unread message, and observe the subscription stream-notify-user(subscriptions-changed) counter and event. Trace the unread-count handling for message deletion. Done means the unread counter decreases and the subscriptions-changed event is emitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100