Page MenuHomePhabricator

[native] Add community name `TextInput` to `CommunityConfiguration`
ClosedPublic

Authored by atul on May 23 2023, 1:20 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 7, 10:57 AM
Unknown Object (File)
Tue, Nov 5, 10:07 PM
Unknown Object (File)
Tue, Nov 5, 9:06 AM
Unknown Object (File)
Tue, Nov 5, 9:06 AM
Unknown Object (File)
Tue, Nov 5, 9:06 AM
Unknown Object (File)
Mon, Nov 4, 10:46 AM
Unknown Object (File)
Mon, Nov 4, 10:46 AM
Unknown Object (File)
Oct 30 2024, 11:51 AM
Subscribers

Details

Summary

Add TextInput field to CommunityConfiguration for user to enter desired community name.


Depends on D7951

Test Plan

Appears as expected, "functionality" will be tested with subsequent diffs.

Simulator Screenshot - Fresh iPhone 14 Pro - 2023-05-23 at 16.21.51.png (2×1 px, 95 KB)

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

atul requested review of this revision.May 23 2023, 1:40 PM
ashoat requested changes to this revision.May 23 2023, 2:26 PM

The placeholder color you're using is super bright. Can you link to designs? Feels like it might be best to stick with what RegistrationTextInput does for consistency

native/community-creation/community-configuration.react.js
50 ↗(On Diff #26916)

The way you're mixing components from different places is weird, but I think it's good that components are being reused in general. Can you make a Linear task to rename / move these general-purpose components somewhere later?

(I did check and they're all using the panel family of colors, which is good for compatibility)

53 ↗(On Diff #26916)

Should we use RegistrationTextInput to maximize reuse / consistency? It uses panelSecondaryForegroundBorder instead of textInputPlaceholder, which is shadesBlack70 in dark mode instead of shadesWhite60. Feels like a pretty significant difference... did Ted really design these interfaces with such a different placeholder color?

This revision now requires changes to proceed.May 23 2023, 2:26 PM
native/community-creation/community-configuration.react.js
50 ↗(On Diff #26916)

Ah yeah intended to leave a comment here flagging this, also reusing RegistrationContainer and RegistrationContentContainer here. Was going to try to generalize naming + possibly move to /components later in the stack. Will create a Linear task to track: https://linear.app/comm/issue/ENG-3929/renamemove-components-used-in-communityconfiguration-to-make-more

53 ↗(On Diff #26916)

We could, but the RegistrationTextInput component looks a lot different than the TextInput in the designs (which more closely resemble inputs in ThreadSettings).

There were no placeholder colors specified in the designs, so I just browsed Figma until I found a text input w/ a similar background and placeholder and copied that. In hindsight I probably should've copied the link down somewhere to reference it....

What I can do now is use the placeholder colors from RegistrationTextInput and then create a Linear task in the DES workspace to follow up w/ @ted when he's back?

use same placeholder colors as RegistrationTextInput:

Simulator Screenshot - Fresh iPhone 14 Pro - 2023-05-24 at 12.08.04.png (2×1 px, 98 KB)

Simulator Screenshot - Fresh iPhone 14 Pro - 2023-05-24 at 12.08.19.png (2×1 px, 98 KB)

This revision is now accepted and ready to land.May 24 2023, 9:27 AM

What I can do now is use the placeholder colors from RegistrationTextInput and then create a Linear task in the DES workspace to follow up w/ @ted when he's back?

Added comment to Linear on existing issue regarding form/input styling consistency: https://linear.app/comm/issue/DES-89/ensure-consistent-forminput-styling-throughout-designs#comment-e61d4350

This revision was landed with ongoing or failed builds.May 24 2023, 9:37 AM
This revision was automatically updated to reflect the committed changes.