feat(transactions): implement memo field utils #7399
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Support the transaction memo for both ICP and ICRC1 addresses for ICP transaction flows. This PR adds utils to validate the provided memo:
memo
field for ICP account transactions is an unsigned 64-bit integer.icrc1Memo
field for ICRC1 account transactions is a byte array with a length of up to 32 bytes.Changes
mapIcpTransactionToUi
to prepare thememo
field for the UI when the value is present. It check first foricrc1Memo
as this value is optional, if not present it uses the value from thememo
field that is always present.isValidIcpMemo
,isValidIcrc1Memo
, andvalidateTransactionMemo
to validate the different types of memos.Tests
Todos