Updated bch-api instance at rest.kingbch.com/v3/ version of bch-api to correct BigNumber issue in hydrateUtxos method.
Re-implemented SLPA txs in CashTab. Also patched BigNumber issue for received SLP txns notifications.
Details
- Reviewers
majcosta alcipir deadalnix - Group Reviewers
Restricted Project - Commits
- rABC6b87d08fce28: Re-enable SLPA transactions in CashTab and fix notification bug
- Create an SLPA token with 9 decimal places or ask me for some.
- npm start
- Send a lot of SLPA tokens back and forth, making sure to check the qty of 0.000000001
Diff Detail
- Repository
- rABC Bitcoin ABC
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
web/cashtab/src/components/Send/SendToken.js | ||
---|---|---|
7 ↗ | (On Diff #26183) | Kind of out of scope, but I would strong recommend using relative path in imports as it makes refactoring significantly more difficult. |
web/cashtab/src/hooks/useBCH.js | ||
310 ↗ | (On Diff #26183) | Remove |
422 ↗ | (On Diff #26183) | This is dead code, also a typical instance of the if/return/else pattern. |
web/cashtab/src/components/Send/SendToken.js | ||
---|---|---|
7 ↗ | (On Diff #26183) | I believe you meant you strong recommend _against_ using relative path. We could switch to @ aliases: https://arunmichaeldsouza.com/blog/aliasing-module-paths-in-node-js |
web/cashtab/src/hooks/useBCH.js | ||
---|---|---|
473–474 ↗ | (On Diff #26183) | I didn't understand this commented code, what is it for? Since we have git can we get rid of it and keep track of these TODOs elsewhere? |
- Remove debug param and commenting
- Handle error if user attempts to send SLPA with no BCHA
- Remove SLPA warning and disabled warning
- Other corrections requested in comments
Can you change the diff title? These "Patching foo" is completely redundant. Yes, this is a patch. That tell us nothing about what this does. Failure to be specific is already having an impact on this diff, asyou are throwing in various other stuff that are "geographically" related, as in they happen in the same area of the code, but are semantically unrelated.