One of our user experiences for tagging a farcaster channel to a community is that we want to allow the user to amnually type the farcaster channel name into a text field to tag the channel if they can't find the channel in the dropdown. This diff introduces all the navigational + boilerplate screen we will need to introduce this user experience
Details
Details
flow + confirmed I was able to navigate to the boilerplate screen
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
This diff has copy changes that need to be reviewed
| native/community-settings/tag-farcaster-channel/tag-farcaster-channel-navigator.react.js | ||
|---|---|---|
| 55 ↗ | (On Diff #39737) | Thought it would make sense to have the header title be the same for both screens, but open to changing it. Regardless this copy should be reviewed |
| native/community-settings/tag-farcaster-channel/tag-farcaster-channel-navigator.react.js | ||
|---|---|---|
| 55 ↗ | (On Diff #39737) | Makes sense to me |
| native/community-settings/tag-farcaster-channel/tag-unfollowed-farcaster-channel.react.js | ||
| 18 ↗ | (On Diff #39737) | “Unfollowed” seems weird to me since it seems to imply that it was first followed and then unfollowed I thought about TagNotFollowedFarcasterChannel and TagCustomFarcasterChannel, but I think I like TagFarcasterChannelByName the best. What do you think? |
| native/community-settings/tag-farcaster-channel/tag-unfollowed-farcaster-channel.react.js | ||
|---|---|---|
| 18 ↗ | (On Diff #39737) | TagFarcasterChannelByName makes sense to me |