You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However the data in the wallet-headless project is defined in camel case style, therefore causing some issues of data compatibility, which force us to duplicate some properties to comply with the snake style too. See the example bellow extracted from the method decodeTx in the wallet.controller.js:
{txId: input.hash,index: input.index,decoded: utxo.decoded,token: utxo.token,value: utxo.value,// This is required by transactionUtils.getTxBalance// It should be ignored by userstoken_data: utxo.token_data,// User facing duplication to keep scheme consistencytokenData: utxo.token_data,script: utxo.script,signed: !!input.data,mine: awaitreq.wallet.isAddressMine(utxo.decoded.address),},
Should we commit with only one style throughout our projects?
The text was updated successfully, but these errors were encountered:
This method
getTxBalance
accepts the inputtx: IHistoryTx
andIHistoryTx
is presented by data in snake case style, as we can see bellow:However the data in the
wallet-headless
project is defined in camel case style, therefore causing some issues of data compatibility, which force us to duplicate some properties to comply with the snake style too. See the example bellow extracted from the methoddecodeTx
in thewallet.controller.js
:Should we commit with only one style throughout our projects?
The text was updated successfully, but these errors were encountered: