-
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
fix: wrong conversation type when resolving 1on1 after receiving new conversation event [WPB-5551] #2248
fix: wrong conversation type when resolving 1on1 after receiving new conversation event [WPB-5551] #2248
Conversation
…conversation event [WPB-5551] (#2247)
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2248 +/- ##
=============================================
- Coverage 57.97% 57.97% -0.01%
Complexity 21 21
=============================================
Files 1081 1081
Lines 41044 41045 +1
Branches 3798 3799 +1
=============================================
Hits 23794 23794
Misses 15625 15625
- Partials 1625 1626 +1
... and 1 file 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
|
…conversation event [WPB-5551] (#2248) * fix: wrong conversation type when resolving 1on1 after receiving new conversation event [WPB-5551] (#2247) * trigger build --------- Co-authored-by: Michał Saleniuk <[email protected]> Co-authored-by: Michał Saleniuk <[email protected]>
Cherry pick from the original PR:
PR Submission Checklist for internal contributors
The PR Title
The PR Description
What's new in this PR?
Issues
New team 1on1 conversations are still not visible on conversation list.
Causes (Optional)
When handling new conversation event, if a conversation is a team 1on1, the app can receive a false type for such conversation instead of . We handle that case when persisting conversation already but shouldn't use field directly anywhere because of that.
Solutions
Use mapping function from to get the proper type when handling new conversation event.
Testing
Test Coverage (Optional)
How to Test
user A and B have no conversation
user A and B use Proteus protocol and at least one does not support MLS protocol (so that MLS can't be used for their 1on1 conversation)
user A and B are in the same team (this assertion was missing in the previous fix)
user B finds user A, opens 1on1 conversation with user A and sends a message
user A can see this new 1on1 conversation on the conversation list even before he/she writes anything in this conversation
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References