-
Notifications
You must be signed in to change notification settings - Fork 26
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: update text input logic to v2 TextFieldState, part 2 [WPB-8779] #3031
Conversation
Ups 🫰🟨This PR is too big. Please try to break it up into smaller PRs. |
Build 4944 failed. |
Test Results930 tests 930 ✅ 16m 52s ⏱️ Results for commit 7f8a502. ♻️ This comment has been updated with latest results. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3031 +/- ##
===========================================
- Coverage 44.32% 44.24% -0.08%
===========================================
Files 450 449 -1
Lines 14521 14526 +5
Branches 2497 2492 -5
===========================================
- Hits 6436 6427 -9
- Misses 7375 7397 +22
+ Partials 710 702 -8
... and 26 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
…-v2-textfieldstate-pt2
Build 4946 succeeded. The build produced the following APK's: |
…-v2-textfieldstate-pt2
APKs built during tests are available here. Scroll down to Artifacts! |
Build 4956 succeeded. The build produced the following APK's: |
…-v2-textfieldstate-pt2 # Conflicts: # app/src/main/kotlin/com/wire/android/ui/authentication/create/code/CreateAccountCodeScreen.kt
Quality Gate passedIssues Measures |
Build 5048 succeeded. The build produced the following APK's: |
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.
LGTM 👍
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Android Compose has new v2 version of text field inputs, and with that, they are going away from the previous approach with
TextFieldValue
andonValueChanged
and replacing it withTextFieldState
.We already updated text fields to v2 but still are using "hybrid" solution which synchronises between
TextFieldValue/onValueChanged
andTextFieldState
.In this PR, following screens, their ViewModels logic and tests are updated to use
TextFieldState
:Also, states for login are split into two dedicated for email login and sso login as having one for both was making a confusion, especially when having instances of all three
LoginViewModel
,LoginEmailViewModel
andLoginSSOViewModel
was giving impression that the state is shared between them but in theory they could have different values.Testing
Test Coverage (Optional)
How to Test
Use text fields from any of listed screens.
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
.