-
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: remove duplicated legalHoldStatus field from ConversationDetails [WPB-4568] #2336
refactor: remove duplicated legalHoldStatus field from ConversationDetails [WPB-4568] #2336
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #2336 +/- ##
=============================================
- Coverage 58.33% 58.33% -0.01%
Complexity 21 21
=============================================
Files 1109 1109
Lines 43287 43283 -4
Branches 4041 4041
=============================================
- Hits 25253 25247 -6
- Misses 16254 16256 +2
Partials 1780 1780
... and 2 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Datadog ReportAll test runs ✅ 2 Total Test Services: 0 Failed, 0 with New Flaky, 2 Passed Test Services
|
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
There were duplicated fields related to legal hold status for conversation - one in
Conversation
data, which is persisted in the DB and also redundant one added to theConversationDetails.OneOne
andConversaionDetails.Group
.Solutions
Remove the
legalHoldStatus
field fromConversationDetails.OneOne
andConversationDetails.Group
because it already containsConversation
data which haslegalHoldStatus
for conversation.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
.