Page MenuHomePhabricator

[native] introduce farcaster account settings profile row
ClosedPublic

Authored by ginsu on Mar 29 2024, 2:29 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 16, 7:40 PM
Unknown Object (File)
Sat, Nov 16, 5:20 PM
Unknown Object (File)
Wed, Nov 13, 12:48 PM
Unknown Object (File)
Sun, Nov 10, 3:42 AM
Unknown Object (File)
Thu, Oct 24, 1:18 PM
Unknown Object (File)
Oct 23 2024, 9:27 AM
Unknown Object (File)
Oct 23 2024, 8:03 AM
Unknown Object (File)
Oct 23 2024, 6:23 AM
Subscribers

Details

Summary

this diff introduces a barebones FarcasterAccountSettings screen + all the navigational logic to get to this screen from the profiles screen. Too make this diff easier to review, subsequent diffs will handle extending FarcasterAccountSettings.

Depends on D11463

Test Plan

Please see the demo video below + tested the entire sign in + unauth flow during the hackathon

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

ginsu edited the test plan for this revision. (Show Details)
ginsu added a reviewer: atul.
ginsu added inline comments.
native/profile/profile-screen.react.js
204–209 ↗(On Diff #38564)

This code lives in a class component, so that is why we are not using useMemo() here

native/profile/profile-screen.react.js
176 ↗(On Diff #38564)

Decided to gate farcasterAccountSettings behind the staffCanSee so that we can internally test this before releasing this to the public

ginsu requested review of this revision.Mar 29 2024, 2:45 PM
native/profile/profile-screen.react.js
176 ↗(On Diff #38564)

I think we're gating it in two other places based on usingCommServicesAccessToken:

  1. FarcasterDataHandler
  2. The new registration flow, which contains the farcaster registration flow

Should we do the same here?

native/profile/profile-screen.react.js
176 ↗(On Diff #38564)

yea that makes sense, I'll update the gate so that it's based off of usingCommServicesAccessToken + __DEV__ rather than staffCanSee

update farcaster account gate logic

native/profile/profile-screen.react.js
241–246 ↗(On Diff #38634)

This code lives in a class component, so that is why we are not using useMemo() here

native/profile/profile-screen.react.js
241–246

This code lives in a class component, so that is why we are not using useMemo() here

atul added inline comments.
native/profile/profile-screen.react.js
241–246

Thanks for noting this

This revision is now accepted and ready to land.Apr 1 2024, 12:46 PM