Change Details

As I am working on bringing the channel tagging UI to `web`, I noticed that I did not properly handle all the error states for the `TagFarcasterChannelByName` screen. At the moment, we only check if the input given by the user is a valid farcaster channel name; however, atm we don't have any logic handling if something went wrong during the keyserver call

As I am working on bringing the channel tagging UI to `web`, I noticed that I did not properly handle all the error states for the `TagFarcasterChannelByName` screen. At the moment, we only check if the input given by the user is a valid farcaster channel name; however, atm we don't have any logic handling if something went wrong during the create farcaster channel tag keyserver call. There was also another issue, where the user would be taken back to previous screen even if the something went wrong during the create farcaster channel tag keyserver call. To address this, I introduced a new optional param to `useCreateFarcasterChannelTag` where we can include logic through a callback to be called only when we successfully finish the create farcaster channel tag keyserver call. Depends on D12541

As I am working on bringing the channel tagging UI to `web`, I noticed that I did not properly handle all the error states for the `TagFarcasterChannelByName` screen. At the moment, we only check if the input given by the user is a valid farcaster channel name; however, atm we don't have any logic handling if something went wrong during the keyserver callcreate farcaster channel tag keyserver call. There was also another issue, where the user would be taken back to previous screen even if the something went wrong during the create farcaster channel tag keyserver call. To address this, I introduced a new optional param to `useCreateFarcasterChannelTag` where we can include logic through a callback to be called only when we successfully finish the create farcaster channel tag keyserver call. Depends on D12541