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
As a part of the objective, we should enable Lisk Desktop to display a summary of custom transaction details implemented based on the Lisk protocol. Lisk Desktop should use the transaction schema provided by Lisk Service to display the transaction in the most readable format.
Acceptance Criteria
Lisk Desktop should be able to:
Display the commonly used data types such as
BigInt
Number
Boolean
String
Address (with an avatar)
Public key
And any array of the above.
Use the transaction schema to determine the data format, and assign the correct component to display field data in the most readable format.
Reasonable unit test coverage is required.
Additional information
Recommendation
The TxSummarizer component implements a series of stateless components that are able to display asset data of transaction types supported by the mainchain.
We should abstract the data format presentation to lower level components and use them in a dynamic component that is able to compose the transaction summary according to the transaction schema and said abstract components.
The text was updated successfully, but these errors were encountered:
Description
As a part of the objective, we should enable Lisk Desktop to display a summary of custom transaction details implemented based on the Lisk protocol. Lisk Desktop should use the transaction schema provided by Lisk Service to display the transaction in the most readable format.
Acceptance Criteria
Additional information
Recommendation
The TxSummarizer component implements a series of stateless components that are able to display asset data of transaction types supported by the mainchain.
We should abstract the data format presentation to lower level components and use them in a dynamic component that is able to compose the transaction summary according to the transaction schema and said abstract components.
The text was updated successfully, but these errors were encountered: