Conversation
…-lib-v2.1.1 * origin/master: chore: bumped to v1.9.0 (#259) chore: nano-testnet-hackaton (#243) fix: address invalid parameter (#235) chore: added htr token seed (#256) fix: invalid assert in release tx proposal utxos (#251) fix: we should await mark utxos with proposal id to prevent a race condition (#250) Merge pull request #248 from HathorNetwork/feat/version-camel-case fix: v1.8.2-rc.3 qa issues (#246) fix: firebase env variables should be optional (#245) chore: remove error handler middleware from authorization lambda (#242) feat: version data validation (#241) fix: Mainnet release script (#203)
|
|
||
| export interface EventTxOutput { | ||
| value: number; | ||
| value: bigint; |
There was a problem hiding this comment.
Is this a full node event? Does the value come as string?
There was a problem hiding this comment.
You are correct, I was changing instances of value to bigint and did not consider how the data is generated.
This comes from the reliable integration, so it is a json event from a fullnode websocket, maybe we should create zod schemas to parse and validate the event data.
There was a problem hiding this comment.
Makes sense to do it in another PR. Can you create an issue so we can track this?
| function abs(num: bigint) { | ||
| return num >= 0n ? num : -num; | ||
| } |
There was a problem hiding this comment.
You had to create this method twice already. Maybe we could have a util bigIntAbs for this. What do you think?
There was a problem hiding this comment.
I did create 2 instances of this method, but both of these were inside a sortBalanceValueByAbsTotal which is a method that is duplicated on the wallet-service and daemon packages.
This issue is because some utilities should be moved to the common package to avoid duplicating code.
So I think we should move the sortBalanceValueByAbsTotal instead of the internal abs and this seems a little outside the scope of this PR which is already huge.
What do you think?
There was a problem hiding this comment.
I agree. Can you create an issue in this repo with this discussion so we can improve this?
…-lib-v2.1.1 * origin/master: chore: nano-testnet bravo (#262)
…ntract-tx * origin/master: chore: upgrade wallet-lib to v2.5.1 (#222)
Acceptance Criteria
Checklist
master, confirm this code is production-ready and can be included in future releases as soon as it gets merged