-
Notifications
You must be signed in to change notification settings - Fork 279
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
feat: adopt new queryReactions endpoint #2388
Conversation
Size Change: +358 B (+0.02%) Total Size: 2.14 MB
ℹ️ View Unchanged
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2388 +/- ##
==========================================
- Coverage 85.31% 85.28% -0.03%
==========================================
Files 392 392
Lines 9021 9025 +4
Branches 2320 2320
==========================================
+ Hits 7696 7697 +1
- Misses 1118 1120 +2
- Partials 207 208 +1 ☔ View full report in Codecov by Sentry. |
## [11.19.0](v11.18.1...v11.19.0) (2024-05-23) ### Bug Fixes * fix aria label translations for Portuguese ([28b6dfd](28b6dfd)) * prevent loading more non-existent thread replies ([#2399](#2399)) ([f2ed479](f2ed479)) * prevent showing link previews in AttachmentPreviewList ([#2398](#2398)) ([cf24894](cf24894)) ### Features * adopt new queryReactions endpoint ([#2388](#2388)) ([d6ca4ef](d6ca4ef))
🎉 This PR is included in version 11.19.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🚂 GetStream/stream-chat-js#1279
The new
queryReactions
endpoint supports backend filtering and sorting, so now we don't have to fetch all reactions and then process them on the client.sortReactionDetails
prop for client-side filtering is still supported, but deprecated. The new recommended way is to passreactionDetailsSort
object which will be passed in the reactions query.