-
Notifications
You must be signed in to change notification settings - Fork 76
feat: add message delivery receipts #1617
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
Size Change: +15.5 kB (+4.59%) 🔍 Total Size: 352 kB
|
src/client.ts
Outdated
async markChannelsDelivered(data?: MarkDeliveredOptions) { | ||
const deliveryReceiptsEnabled = | ||
this.user?.privacy_settings?.delivery_receipts?.enabled; | ||
if (!deliveryReceiptsEnabled) return; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we could return some feedback to know that the privacy_setting is missing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't plan it in this PR.
…if does not exist in the event
… OwnMessageReceiptsTracker
# Conflicts: # src/client.ts
3675474
to
eabae00
Compare
🎉 This PR is included in version 9.22.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Goal
Provide:
service for buffering of delivery confirmation payload (
client.deliveryReportCoordinator
is handling the buffering and throttling of the requests). See Buffering service section in the spec.WS event processing for read state updates (
message.new
,message.read
,notification.mark_unread
,notification.channel_delivered
- name may change)Closes REACT-501
Spec
See description of CHA-991
Out of scope
The buffering service is prepared to handle delivery confirmation for threads too, but it is disabled for the moment.