-
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] #2247
Merged
saleniuk
merged 1 commit into
release/candidate
from
fix/wrong-type-when-resolving-1on1
Nov 22, 2023
Merged
fix: wrong conversation type when resolving 1on1 after receiving new conversation event [WPB-5551] #2247
saleniuk
merged 1 commit into
release/candidate
from
fix/wrong-type-when-resolving-1on1
Nov 22, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…conversation event [WPB-5551]
github-actions
bot
added
🚨 Potential breaking changes
👕 size: S
type: bug / fix 🐞
labels
Nov 22, 2023
mchenani
approved these changes
Nov 22, 2023
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release/candidate #2247 +/- ##
====================================================
Coverage ? 58.06%
Complexity ? 21
====================================================
Files ? 1074
Lines ? 40766
Branches ? 3776
====================================================
Hits ? 23670
Misses ? 15475
Partials ? 1621 Continue to review full report in Codecov by Sentry.
|
saleniuk
requested review from
a team,
typfel,
yamilmedina,
borichellow,
MohamadJaara and
vitorhugods
and removed request for
a team
November 22, 2023 14:26
alexandreferris
approved these changes
Nov 22, 2023
yamilmedina
approved these changes
Nov 22, 2023
7 tasks
github-actions bot
pushed a commit
that referenced
this pull request
Nov 22, 2023
…conversation event [WPB-5551] (#2247)
github-merge-queue bot
pushed a commit
that referenced
this pull request
Nov 24, 2023
…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]>
augustocdias
pushed a commit
that referenced
this pull request
Dec 5, 2023
…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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
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
GROUP
type for such conversation instead ofONE_TO_ONE
. We handle that case when persisting conversation already but shouldn't usetype
field directly anywhere because of that.Solutions
Use mapping function from
ConversationMapper
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
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.