-
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(mls): reevaluate protocol on demand [WPB-5049] #2278
Conversation
Introduced a new UseCase, NotifyConversationIsOpenUseCase, to notify when a conversation is open. This new use case allows the performing of update operations like protocol reevaluation in a lazy manner when a conversation is opened. This addition improves the app's responsiveness when user navigates to it, in case there was no protocol migration before.
Test Results1 888 tests - 778 1 858 ✔️ - 704 14s ⏱️ - 2m 4s Results for commit 96eded9. ± Comparison against base commit 2c6d056. This pull request removes 2666 and adds 1888 tests. Note that renamed tests count towards both.
This pull request removes 104 skipped tests and adds 30 skipped tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2278 +/- ##
==========================================
Coverage 57.86% 57.87%
Complexity 21 21
==========================================
Files 1086 1087 +1
Lines 41068 41090 +22
Branches 3804 3805 +1
==========================================
+ Hits 23763 23779 +16
- Misses 15702 15707 +5
- Partials 1603 1604 +1
... and 2 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
...monMain/kotlin/com/wire/kalium/logic/feature/conversation/NotifyConversationIsOpenUseCase.kt
Outdated
Show resolved
Hide resolved
Datadog ReportAll test runs ✅ 2 Total Test Services: 0 Failed, 0 with New Flaky, 2 Passed Test Services
|
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.
just checking the ids on the log 🤔
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
We should have a fallback / safety net for 1:1 migrations.
Solutions
Expose a way to notify Kalium that a conversation is being displayed to the user.
This way, Kalium can do some sanity checks.
When calling
NotifyConversationIsOpenUseCase
, Kalium can check if the conversation is 1:1 and if its protocol is up-to-date.Testing
Test Coverage
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.