refactor: update text input logic to v2 TextFieldState, part 3 [WPB-8779] #3054
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?
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
: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
.