Page MenuHomePhabricator

[native] show error message for tag farcaster channel errors
ClosedPublic

Authored by ginsu on Apr 26 2024, 12:03 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 11, 9:06 AM
Unknown Object (File)
Mon, Nov 11, 4:46 AM
Unknown Object (File)
Mon, Nov 11, 2:19 AM
Unknown Object (File)
Mon, Nov 11, 12:02 AM
Unknown Object (File)
Sun, Nov 10, 6:22 PM
Unknown Object (File)
Oct 15 2024, 11:20 PM
Unknown Object (File)
Oct 11 2024, 7:13 AM
Unknown Object (File)
Oct 11 2024, 7:13 AM
Subscribers

Details

Summary

This diff improves the error handling for creating a farcaster tag blob. If there is an error we will display a message to the user for why the request failed

Depends on D11793

Test Plan

Please see the demo video below

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 reviewers: atul, inka.
ginsu added a reviewer: ashoat.

This diff introduces new copy

native/community-settings/tag-farcaster-channel/tag-farcaster-channel.react.js
26 ↗(On Diff #39586)

This copy needs to be reviewed

164 ↗(On Diff #39586)

Copy needs to be reviewed

Copy looks okay. Thought about whether we could filter the list of channels before it gets to the keyserver, but we'd probably need a UI to show which ones are already taken, in addition to logic on the client to check each channel with the blob service. Probably too much additional complexity to be worth doing at this time

inka added inline comments.
native/community-settings/tag-farcaster-channel/tag-farcaster-channel.react.js
94 ↗(On Diff #39586)

Can we move this to onOptionSelected? If you disagree I won't insist, but it seems more natural to me that the error would disappear only once a different item is picked

This revision is now accepted and ready to land.Apr 30 2024, 8:58 AM

address comments + rebase before landing

Thought about whether we could filter the list of channels before it gets to the keyserver, but we'd probably need a UI to show which ones are already taken, in addition to logic on the client to check each channel with the blob service. Probably too much additional complexity to be worth doing at this time

Agree this would be nice to have, but also agree that this should be considered out of scope for now. I created a linear task to track this piece of feedback:

https://linear.app/comm/issue/ENG-8032/filter-list-of-taken-farcaster-channels

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