Page MenuHomePhabricator

[native] refactor registration button to be submit button
Needs RevisionPublic

Authored by ginsu on May 1 2024, 11:04 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 11, 4:29 AM
Unknown Object (File)
Mon, Nov 11, 3:11 AM
Unknown Object (File)
Sun, Nov 10, 12:44 PM
Unknown Object (File)
Mon, Oct 21, 8:58 AM
Unknown Object (File)
Oct 11 2024, 6:56 AM
Unknown Object (File)
Oct 11 2024, 6:56 AM
Unknown Object (File)
Oct 11 2024, 6:56 AM
Unknown Object (File)
Sep 18 2024, 7:53 PM
Subscribers

Details

Reviewers
inka
ashoat
Summary

Plan to be using this button in subsquent diffs. I figured since this button is used more generally than just for the registration we should rename this to be SubmitButton

Depends on D11855

Test Plan

flow

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

ginsu requested review of this revision.May 1 2024, 11:20 PM
  1. I don't think SubmitButton is a great name for this. It's used for actions other than submitting.
  2. I don't think it makes sense to move this component out by itself. It's tightly coupled to the other visual components in the native/account/registration folder, and now it's pretty weird that some of them are in that folder and some are elsewhere.

Some time ago Atul created a task to track moving some of the general-purpose visual components in native/account/registration elsewhere: ENG-3929. There I suggested using the name prefix Panel, eg. PanelButton.

We already have a PanelButton and a Panel, but we could rename those first, eg. to LegacyPanelButton or LoginPanelButton.

Some concrete suggestions:

  1. Rename existing PanelButton, Panel, etc.
  2. Go with PanelButton for this component
  3. Create a separate folder for it inside native/components (eg. native/components/panel)
  4. Move and rename the other related visual components too
ashoat requested changes to this revision.May 2 2024, 8:58 AM
This revision now requires changes to proceed.May 2 2024, 8:58 AM

Removing this diff from the diff stack and will address the feedback for this in a separate diff stack