Page MenuHomePhabricator

[Cashtab][Alias] Remove redundant node error translation in handleAliasRegistrationError
ClosedPublic

Authored by emack on Oct 13 2023, 04:59.

Details

Summary

T3316

The 'too many unconfirmed ancestors' node error is no longer applicable in handleAliasRegistrationError, hence removing the error translation logic.

Test Plan

Attempt to register a new alias on a wallet with insifficient funds and ensure the node error is rendered as a UI pop up
grep -r handleAliasRegistrationError src/

Diff Detail

Repository
rABC Bitcoin ABC
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

emack requested review of this revision.Oct 13 2023, 04:59
The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience.
The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience.

image.png (524×522 px, 89 KB)

Was a transient failure, I restarted the build and it's green

There was no test for this ?

There was no test for this ?

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:

  • manual test above to observe the error message pop up in the frontend
  • grep -r handleAliasRegistrationError src/ to ensure no dependency on this removed function from anywhere else in Cashtab
This revision is now accepted and ready to land.Oct 13 2023, 17:18