-
Notifications
You must be signed in to change notification settings - Fork 290
fix: show the message status only for the last own message when returnAllReadData is false #2877
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…nAllReadData is false
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #2877 +/- ##
==========================================
- Coverage 81.50% 81.47% -0.03%
==========================================
Files 497 499 +2
Lines 10082 10105 +23
Branches 2306 2310 +4
==========================================
+ Hits 8217 8233 +16
- Misses 1745 1752 +7
Partials 120 120 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Size Change: +1.55 kB (+0.13%) Total Size: 1.18 MB
ℹ️ View Unchanged
|
## [13.10.1](v13.10.0...v13.10.1) (2025-10-30) ### Bug Fixes * show the message status only for the last own message when returnAllReadData is false ([#2877](#2877)) ([7e47fda](7e47fda))
|
🎉 This PR is included in version 13.10.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎯 Goal
Closes REACT-624
🛠 Implementation details
The sent status was rendered for every own message (group) even though the returnAllReadData was disabled meaning that it should have been shown only for the last own message.
I do not like this solution very much but it is in line with what is the current SDK architecture - have a value and propagate it down not forgetting about memoization dependencies.