Repository navigation
design(ui): convert IncrementerNumberPicker to Compose - #22846
david-allison wants to merge 5 commits into
Conversation
|
Snapshot diff report vs
All 16 changed screenshotsBackupPickerScreenshotTest
|
4784eb9 to
ecf4a59
Compare
Assisted-by: GPT-6.1-Sol xhigh
Assisted-by: GPT-6.1-Sol xhigh
* 1:1 design * native numeric field interop * existing input connection code * existing accessibility behavior Assisted-by: GPT-6.1-Sol xhigh
* backup preferences only (for now) Screenshots are byte-identical Prep for moving 'reposition' to this dialog Assisted-by: GPT-6.1-Sol xhigh
'done' & 'enter' press the 'save' button if available. Assisted-by: GPT-6.1-Sol xhigh
ecf4a59 to
9a85386
Compare
mikehardy
left a comment
There was a problem hiding this comment.
Assisted-by: Grok 4.7
Thank you — wiring IME Done/Enter through the enabled Save button keeps the incrementer honest without changing the range rules.
Locally I rebased onto main without force-pushing (prep stayed at the PR tip). I ran lint (lintAll, ktlintCheck, lint-rules:test), unit tests (jacocoUnitTestReport), and release emulator tests (TEST_RELEASE_BUILD=true via run_emulator_tests.py on emulator-5556 / API35_GAPI); all passed.
Reviewed the shared Compose IncrementerNumberPicker hosted from IncrementerNumberRangePreferenceCompat, validation in NumberPickerState, backup-picker Roborazzi/input/a11y coverage, and Done/Enter performing the positive button only when in-range so cancel and bad input do not persist.
some acceptable findings, no action required, just leaving for posterity: backup test artifacts under filesDir/backup-picker are write-only; screenshot test header still mentions comparing old vs new picker though it captures the current dialog once.
Screenshot changes have been detected, so leaving this for a good manual look.
















Note
Assisted-by: GPT-6.1-Sol xhigh
Purpose / Description
Approach
doneclosed the soft keyboard, rather than submitting the dialogHow Has This Been Tested?
Screenshot tests are 1:1 matching
Checklist