Refactor total unread message count
Goal
Improve accuracy of total unread message count
What needs to be done
TODO: Do we need to do some changes for message level unread timestamps to?
Either:
- Emit from sockets on new event to tell clients to refresh total count.
- Emit from sockets on new event with total count, to tell clients to update thier count from the number in the event.
- Have the unread query support a timestamp
Acceptance Criteria
-
Total unread count works accurately -
Room level unread notifications work accurately. -
Spin up follow-up card for mobile post-merge.
QA
Test AC.
UX/Design
N/A
Mobile
-
Is Mobile Required?
Following engine changes.
Personas
Chat users.
Experiments
N/A
Definition of Ready Checklist
-
Definition Of Done (DoD) -
Acceptance criteria -
Weighted -
QA -
UX/Design -
Personas -
Experiments