Page MenuHomePhabricator

[Cashtab] [chronik tx history p14]Remove legacy tx parsing functions, tests, and mocks
ClosedPublic

Authored by bytesofman on Oct 4 2022, 19:26.

Details

Summary

T2447

Depends on D12139

Remove all legacy tx history parsing functions associated with the bch-api approach. Also remove their related unit tests and mocks.

Test Plan

Review removed functions. grep -r <functionName> src/ for each to confirm they are not used anywhere else in the codebase.

npm start and app still works

Diff Detail

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

Event Timeline

emack requested changes to this revision.Oct 5 2022, 12:54
emack added a subscriber: emack.
  1. to avoid new dev confusion in chronik.js:

change:

// Defining variables used in lines legacy parseTxData function from useBCH.js

to

// Defining variables used in line with the now removed legacy parseTxData function from useBCH.js

  1. Also I'm seeing a reference to getTxHistory() in useWallet.js.rej - can we ignore this as this seems to be a arc patch artefact?

image.png (364×1 px, 149 KB)

Otherwise app tested all ok after these deprecations. If anything, the speed improvement from this diff is VERY noticeable.

This revision now requires changes to proceed.Oct 5 2022, 12:54
  1. to avoid new dev confusion in chronik.js:

change:

// Defining variables used in lines legacy parseTxData function from useBCH.js

to

// Defining variables used in line with the now removed legacy parseTxData function from useBCH.js

  1. Also I'm seeing a reference to getTxHistory() in useWallet.js.rej - can we ignore this as this seems to be a arc patch artefact?

image.png (364×1 px, 149 KB)

Otherwise app tested all ok after these deprecations. If anything, the speed improvement from this diff is VERY noticeable.

Handled this in D12148

Diffs after this make the comment obsolete

  1. Also I'm seeing a reference to getTxHistory() in useWallet.js.rej - can we ignore this as this seems to be a arc patch artefact?

image.png (364×1 px, 149 KB)

Yeah you can just delete the file.

This revision is now accepted and ready to land.Oct 5 2022, 23:13