Page MenuHomePhabricator

[native] introduce barebones TagFarcasterChannelNavigator + TagFarcasterChannel screen
ClosedPublic

Authored by ginsu on Apr 14 2024, 10:09 PM.
Tags
None
Referenced Files
F3383106: D11662.id39205.diff
Thu, Nov 28, 1:38 PM
F3383068: D11662.id39101.diff
Thu, Nov 28, 1:24 PM
Unknown Object (File)
Sun, Nov 24, 10:56 PM
Unknown Object (File)
Sun, Nov 24, 9:48 PM
Unknown Object (File)
Sun, Nov 24, 9:39 PM
Unknown Object (File)
Sun, Nov 24, 9:11 PM
Unknown Object (File)
Sun, Nov 24, 7:37 PM
Unknown Object (File)
Fri, Nov 8, 4:43 PM
Subscribers

Details

Summary

This diff introduces the barebones navigational logic needed for introducing TagFarcasterChannelNavigator and the TagFarcasterChannel screen. Subsquent diffs will handle extending both of these to match the UI/UX with the rest of the app

Linear tasks: https://linear.app/comm/issue/ENG-7538/introduce-tag-farcaster-channel-option-in-the-community-actions-menu + https://linear.app/comm/issue/ENG-7539/introduce-tagfarcasterchannelmodal-screen + https://linear.app/comm/issue/ENG-7540/introduce-navigational-logic-for-tagfarcasterchannelmodal

Test Plan

flow + confirmed that I could navigate to TagFarcasterChannel from community action buttons

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ginsu added reviewers: atul, inka.
ginsu added inline comments.
native/community-settings/tag-farcaster-channel/tag-farcaster-channel.react.js
19 ↗(On Diff #39102)

This will be updated in subsequent diffs

native/components/community-actions-button.react.js
37 ↗(On Diff #39102)

Added theses new lines to space out the code in this file

Looks good, let's definitely memoize return value of TagFarcasterChannelNavigator.

native/community-settings/tag-farcaster-channel/tag-farcaster-channel-navigator.react.js
41–50 ↗(On Diff #39102)

Would be good to memoize this since we've got a Navigator and entire screens.

native/components/community-actions-button.react.js
118–120 ↗(On Diff #39102)

Has this copy been signed off on?
Is "Tag" the verb we've decided on to be product facing?

Just want to double check since I don't have context here. (CC @ashoat)

This revision is now accepted and ready to land.Apr 15 2024, 4:36 PM
native/components/community-actions-button.react.js
118–120 ↗(On Diff #39102)

This works, but this is the kind of thing I'd like sign-off for

native/components/community-actions-button.react.js
118–120 ↗(On Diff #39102)

My bad, definitely should have done that. Will be more thoughtful about this

ginsu edited the summary of this revision. (Show Details)

address comments + update gating logic for showing tag farcaster channel to check fid is present as well

ginsu added inline comments.
native/components/community-actions-button.react.js
40–43 ↗(On Diff #39200)

Another usage of fidContext @will

124–125 ↗(On Diff #39200)

Snuck in this change in the latest update of my diff. The change here is that canTagFarcasterChannel also now checks if there is an fid set. Felt like it didn't make sense to be able to access this screen if you aren't connected to farcaster (fid is not set)

native/components/community-actions-button.react.js
121–124 ↗(On Diff #39205)

Snuck in this change in the latest update of my diff. The change here is that canTagFarcasterChannel also now checks if there is an fid set and that community is not GENESIS.

Felt like it didn't make sense to be able to access this screen if you aren't connected to farcaster (fid is not set) and tagging GENESIS to a farcaster channel also did not make sense to me

This revision was landed with ongoing or failed builds.Apr 18 2024, 9:24 AM
This revision was automatically updated to reflect the committed changes.