-
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
refactor: optimise legal hold discovery when handling new message and unify fetching clients [WPB-5837] #2334
refactor: optimise legal hold discovery when handling new message and unify fetching clients [WPB-5837] #2334
Conversation
… unify fetching clients
Test Results1 997 tests - 809 1 967 ✔️ - 735 12s ⏱️ - 2m 49s Results for commit 942e17a. ± Comparison against base commit 19491b1. This pull request removes 2806 and adds 1997 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 ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #2334 +/- ##
=============================================
- Coverage 58.34% 58.33% -0.01%
Complexity 21 21
=============================================
Files 1109 1109
Lines 43291 43287 -4
Branches 4041 4041
=============================================
- Hits 25258 25252 -6
- Misses 16254 16256 +2
Partials 1779 1779
... and 4 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
…d-discovery-when-receiving-message
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
When handling client changes when receiving new message, to check whether the given member's legal hold status is changed, a list of member's clients was fetched separately in a loop which is time and resource consuming.
Solutions
Now, clients for all members from all conversations with updated legal hold status are fetched in a single request.
Additionally, use cases names for fetching clients are unified and the one for fetching clients for other members is modified to take a list of user ids instead of a single one for more versatility.
Testing
Test Coverage (Optional)
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
.