Page MenuHomePhabricator

[native] introduce getFarcasterAccountAlreadyLinkedAlertDetails
ClosedPublic

Authored by ginsu on May 3 2024, 11:38 PM.
Tags
None
Referenced Files
F3388935: D11873.id39779.diff
Fri, Nov 29, 4:42 PM
F3388663: D11873.id40246.diff
Fri, Nov 29, 3:31 PM
Unknown Object (File)
Thu, Nov 21, 9:59 PM
Unknown Object (File)
Tue, Nov 12, 11:25 AM
Unknown Object (File)
Tue, Nov 12, 8:07 AM
Unknown Object (File)
Tue, Nov 12, 8:05 AM
Unknown Object (File)
Sun, Nov 10, 11:42 AM
Unknown Object (File)
Fri, Nov 8, 7:16 PM
Subscribers

Details

Summary

Based on feedback in D11863, I want to factor out the logic for this error message since it will be needed in several places.

Test Plan

flow + confirmed the error message was the same

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

native/utils/alert-messages.js
34

Took a second to have all of these be exported in the bottom of the file, which is a more common pattern I see in our codebase

ginsu requested review of this revision.May 3 2024, 11:54 PM
ashoat added inline comments.
native/account/registration/connect-farcaster.react.js
114

Just wondering, why rename body with message?

native/utils/alert-messages.js
55

Should all of these start with a lowercase letter? I thought we only use uppercase for React components (and sometimes all caps for constants)

This revision is now accepted and ready to land.May 4 2024, 11:19 AM
native/account/registration/connect-farcaster.react.js
114

I wanted this to match the AlertDetails type. However, I should have also updated the queuedAlert state to use this type too. Will make this update

native/utils/alert-messages.js
55

address comments + rebase before landing