Change Details

T3216 This diff refactors Alias.js to connect to the new alias-server endpoints to check: - alias availability - aliases registered to the active wallet These were not pushed as two separate diffs because they are dependent on each other e.g. once an alias is confirmed to be available and is then registered, the reviewer needs the 'aliases registered to address' component to be hooked up to alias-server at the same time to verify the registration on the Alias.js page. ~~ Reviewer notes: - pending alias retrieval is still WIP on alias-server so in order to verify this diff you'll need to wait until that registration tx has been confirmed and then refresh the Alias page to see the recently registered alias reflected. - Once the pending alias feasure is available in alias-server then the 'aliases registered to address' check in useEffect() will render both registered and pending aliases, hence no need to separately worry about adding '(pending)' to the end of each newly registered aliases at the point of registration. ~~

T3216 This diff refactors Alias.js to connect to the new alias-server endpoints to check: - alias availability - aliases registered to the active wallet These were not pushed as two separate diffs because they are dependent on each other e.g. once an alias is confirmed to be available and is then registered, the reviewer needs the 'aliases registered to address' component to be hooked up to alias-server at the same time to verify the registration on the Alias.js page.

T3216 This diff refactors Alias.js to connect to the new alias-server endpoints to check: - alias availability - aliases registered to the active wallet These were not pushed as two separate diffs because they are dependent on each other e.g. once an alias is confirmed to be available and is then registered, the reviewer needs the 'aliases registered to address' component to be hooked up to alias-server at the same time to verify the registration on the Alias.js page. ~~ Reviewer notes: - pending alias retrieval is still WIP on alias-server so in order to verify this diff you'll need to wait until that registration tx has been confirmed and then refresh the Alias page to see the recently registered alias reflected. - Once the pending alias feasure is available in alias-server then the 'aliases registered to address' check in useEffect() will render both registered and pending aliases, hence no need to separately worry about adding '(pending)' to the end of each newly registered aliases at the point of registration. ~~