Page MenuHomePhabricator

[native] improve error handling for TagUnfollowedFarcasterChannel screen
ClosedPublic

Authored by ginsu on May 6 2024, 12:09 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 11, 2:43 AM
Unknown Object (File)
Sun, Nov 10, 6:30 PM
Unknown Object (File)
Sun, Nov 10, 3:12 PM
Unknown Object (File)
Sun, Nov 10, 11:41 AM
Unknown Object (File)
Fri, Nov 8, 7:18 PM
Unknown Object (File)
Fri, Nov 8, 7:18 PM
Unknown Object (File)
Thu, Oct 24, 8:53 AM
Unknown Object (File)
Oct 18 2024, 11:38 PM
Subscribers

Details

Summary

This diff improves the error handling for TagUnfollowedFarcasterChannel by providing a few error messages to the user based on the error.message that was given

Depends on D11866

Test Plan

Please see the screenshots below

Screenshot 2024-05-06 at 3.06.48 AM.png (1×1 px, 706 KB)

Screenshot 2024-05-06 at 3.07.18 AM.png (1×1 px, 703 KB)

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

native/community-settings/tag-farcaster-channel/tag-farcaster-channel-by-name.react.js
21

This copy was approved in D11809

22

This copy needs to be reviewed

ginsu requested review of this revision.May 6 2024, 12:26 AM

padding around error message looks different than in invite links, can we make it more consistent?

image.png (402×710 px, 56 KB)

native/community-settings/tag-farcaster-channel/tag-farcaster-channel-by-name.react.js
21

Can we avoid copy-pasting and have this defined in one place?

native/community-settings/tag-farcaster-channel/tag-farcaster-channel-utils.js
5 ↗(On Diff #39865)

This copy needs to be reviewed

padding around error message looks different than in invite links, can we make it more consistent?

Updated the padding to match the screens of invite links which had 8px of padding above and below the error message

Screenshot 2024-05-06 at 1.36.52 PM.png (1×948 px, 523 KB)

Just one comment on the copy

native/community-settings/tag-farcaster-channel/tag-farcaster-channel-utils.js
5 ↗(On Diff #39865)

Let's go with "Could not" instead of "Cannot"

This revision is now accepted and ready to land.May 7 2024, 5:11 AM
This revision was landed with ongoing or failed builds.May 7 2024, 10:17 AM
This revision was automatically updated to reflect the committed changes.