-
Notifications
You must be signed in to change notification settings - Fork 19
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: conversation creation conflict backends dialog #1998
feat: conversation creation conflict backends dialog #1998
Conversation
Build 632 failed. |
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
Codecov Report
@@ Coverage Diff @@
## develop #1998 +/- ##
=============================================
+ Coverage 38.51% 38.55% +0.03%
- Complexity 893 895 +2
=============================================
Files 287 287
Lines 11335 11347 +12
Branches 1459 1460 +1
=============================================
+ Hits 4366 4375 +9
- Misses 6541 6544 +3
Partials 428 428
Continue to review full report in Codecov by Sentry.
|
APKs built during tests are available here. Scroll down to Artifacts! |
Build 642 succeeded. The build produced the following APK's: |
app/src/main/kotlin/com/wire/android/ui/home/newconversation/NewConversationViewModel.kt
Show resolved
Hide resolved
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
APKs built during tests are available here. Scroll down to Artifacts! |
Build 673 succeeded. The build produced the following APK's: |
… github.com:wireapp/wire-android-reloaded into feat/conversation-creation-conflict-backends-dialog
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
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.
Great work!
I just have a tiny comment but not sure if it is the focus on this PR and if it should be changed here
app/src/test/kotlin/com/wire/android/ui/home/newconversation/NewConversationViewModelTest.kt
Outdated
Show resolved
Hide resolved
app/src/test/kotlin/com/wire/android/ui/home/newconversation/NewConversationViewModelTest.kt
Outdated
Show resolved
Hide resolved
APKs built during tests are available here. Scroll down to Artifacts! |
Build 677 succeeded. The build produced the following APK's: |
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
app/src/test/kotlin/com/wire/android/ui/home/newconversation/NewConversationViewModelTest.kt
Outdated
Show resolved
Hide resolved
app/src/test/kotlin/com/wire/android/ui/home/newconversation/NewConversationViewModelTest.kt
Show resolved
Hide resolved
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
1 similar comment
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
APKs built during tests are available here. Scroll down to Artifacts! |
Build 688 succeeded. The build produced the following APK's: |
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
We are not handling federation not fully connected graphs error on group creation
Causes (Optional)
We show unknown error
Solutions
Show dialog for this error with options
Attachments (Optional)
Attachments like images, videos, etc. (drag and drop in the text box)
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
.