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
Following up our effort in #4245, this ticket aims to make the transaction details view blockchain agnostic.
Acceptance Criteria
Lisk Desktop must be able to display the details of transactions that may use more than one token for different values.
All relevant components and utility functions must reside under the transaction domain.
If the asset of the transaction object can not be parsed (displayed using key-value components) then we should display the asset object as beautified JSON.
Update unit tests.
Update and enable relevant e2e tests.
Additional Information
We need the transaction object schema from Lisk Service to understand how to read the data from the transaction object.
The text was updated successfully, but these errors were encountered:
Description
Following up our effort in #4245, this ticket aims to make the transaction details view blockchain agnostic.
Acceptance Criteria
transaction
domain.Additional Information
We need the transaction object schema from Lisk Service to understand how to read the data from the transaction object.
The text was updated successfully, but these errors were encountered: