Page MenuHomePhabricator

[native] Minor updates to UsernameSelection
ClosedPublic

Authored by ashoat on May 25 2023, 12:12 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Mar 12, 8:00 PM
Unknown Object (File)
Thu, Mar 7, 7:45 AM
Unknown Object (File)
Thu, Mar 7, 7:45 AM
Unknown Object (File)
Thu, Mar 7, 7:45 AM
Unknown Object (File)
Tue, Mar 5, 11:48 PM
Unknown Object (File)
Feb 20 2024, 10:09 AM
Unknown Object (File)
Feb 20 2024, 8:57 AM
Unknown Object (File)
Feb 19 2024, 9:54 PM
Subscribers

Details

Summary

Two things I noticed while working on PasswordSelection:

  1. The same returnKeyType="go" change that I included in the previous diff (D7989).
  2. When checkUsernameValidity is called, if the username is valid we will now clear the usernameError.

Depends on D7989

Test Plan
  1. For returnKeyType="go", I confirmed the button was changed. For a visual indication of the change, check the previous diff.
  2. For the checkUsernameValidity change, I triggered a username error by typing in an invalid username (eg. starting with a - character). Then I focused the keyboard, fixed the error, and then dismissed the keyboard. I confirmed that the error text disappeared after the dismissal.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

native/account/registration/username-selection.react.js
54 ↗(On Diff #27076)

I flipped the order of the conditions since they now had the same amount of code, and I figured it made more sense to have the "default" condition at end, in part for consistency with PasswordSelection which has two possible error states

This revision is now accepted and ready to land.May 25 2023, 2:00 PM