T3316
The 'too many unconfirmed ancestors' node error is no longer applicable in handleAliasRegistrationError, hence removing the error translation logic.
Differential D14638
[Cashtab][Alias] Remove redundant node error translation in handleAliasRegistrationError emack on Oct 13 2023, 04:59. Authored by
Details
T3316 The 'too many unconfirmed ancestors' node error is no longer applicable in handleAliasRegistrationError, hence removing the error translation logic. Attempt to register a new alias on a wallet with insifficient funds and ensure the node error is rendered as a UI pop up
Diff Detail
Event TimelineComment Actions The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience. Comment Actions The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience. Comment Actions This is in that same category a few months ago where internal functions (e.g. registerAlias in this case) in a React component (a rendering class) can't be accessed directly. You can only test the initial state and props upon initialization but cases where we need to trigger a custom event (server outage) and then verify its reaction to that event is a challenge with how unit tests are currently set up in Cashtab. This is mitigated by:
|