-
Notifications
You must be signed in to change notification settings - Fork 6
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: Recently ended call metadata [WPB-14256] #3112
base: develop
Are you sure you want to change the base?
Conversation
callMetadata: CallMetadata, | ||
callEndReason: Int | ||
) { | ||
_recentlyEndedCallFlow.tryEmit( |
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.
please also check #3113 as this changes this solution to a more compact which does not expose that much
Bencher Report
Click to view all benchmark results
|
Datadog ReportBranch report: ✅ 0 Failed, 3187 Passed, 107 Skipped, 35.53s Total Time |
Quality Gate passedIssues Measures |
https://wearezeta.atlassian.net/browse/WPB-14256
What's new in this PR?
Issues
We need to add
Call ended
segementationCauses (Optional)
We need raw end call cause and a lot of data. In this PR we're storing recently ended call and give an use case
to create the metadata. I've also have the
compact
version of it (I will link it shortly) that is creating the metadata right away.Solutions
Pick up all the things we need, prepare metadata and allow clients to observe them to use them in the analytics
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.