-
Notifications
You must be signed in to change notification settings - Fork 320
Migrate DropdownViewHolderFactory to compose #2898
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
base: master
Are you sure you want to change the base?
Conversation
2e9773f to
6f0ce2c
Compare
6f0ce2c to
da3a8b7
Compare
jingtang10
left a comment
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.
add a video
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.
Laz said this is actually an instrumentation test - in that case the file needs to be renamed.
if this is a problem with other compose tests we need to rename those test files too.
|
Before Screen_recording_20251111_001344.mp4After Screen_recording_20251111_011254.mp4 |
FikriMilano
left a comment
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
| remember(selectedOption, options) { mutableStateOf(selectedOption) } | ||
|
|
||
| // Track if change is from user typing | ||
| var isUserTyping by remember(options) { mutableStateOf(false) } |
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.
this is not for when the user is actively typing.. this is true after the user started typing but have not made any selections.
add a small comment to explain this.
also maybe call this "in filter mode"? i'll leave it to you to decide what's the best name.
IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #2861
Description
Clear and concise code change description.
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)
Screenshots (if applicable)
Checklist
./gradlew spotlessApplyand./gradlew spotlessCheckto check my code follows the style guide of this project../gradlew checkand./gradlew connectedCheckto test my changes locally.