Page MenuHomePhabricator

[native] Make Farcaster required in new registration flow
ClosedPublic

Authored by ashoat on May 9 2024, 7:56 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 3, 3:15 AM
Unknown Object (File)
Oct 12 2024, 11:13 AM
Unknown Object (File)
Oct 12 2024, 11:13 AM
Unknown Object (File)
Oct 12 2024, 11:13 AM
Unknown Object (File)
Oct 12 2024, 11:13 AM
Unknown Object (File)
Oct 12 2024, 11:13 AM
Unknown Object (File)
Oct 12 2024, 11:13 AM
Unknown Object (File)
Oct 12 2024, 11:13 AM
Subscribers

Details

Summary

Only making it required on release builds to avoid making testing more difficult for devs.

Depends on D11973

Test Plan

Replaced usage of __DEV__ with a hardcoded variable. Tested opening the registration flow from the main screen and from FullscreenSIWEPanel. Make sure CoolOrNerdModeSelection and KeyserverSelection don't appear. Make sure that I am able to successfully register

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

ashoat requested review of this revision.May 9 2024, 8:13 AM
native/account/registration/connect-farcaster.react.js
186 ↗(On Diff #40022)

How about staff users? I know this is about registration, but are we going to require a Farcaster account for possible new developers?

native/account/registration/connect-farcaster.react.js
186 ↗(On Diff #40022)

Good point, I can add an exception for staff builds

useStaffCanSee to allow staff to circumvent Farcaster requirement

ginsu added inline comments.
native/components/farcaster-prompt.react.js
30

Nit/unsolicited, but I think we can drop "currently". Will defer to you to make the final call

This revision is now accepted and ready to land.May 9 2024, 1:06 PM
native/components/farcaster-prompt.react.js
30

I'd rather keep it

This revision was landed with ongoing or failed builds.May 9 2024, 1:11 PM
This revision was automatically updated to reflect the committed changes.