The transactions table is implemented as a custom component <transactions :walletId="...">, which takes a wallet ID, fetch transactions data associated with the ID (dummy data for now) and render it. However, depending on the structure of wallet/transaction API, it might be better to directly pass the data as a prop.
Wallet page scrolls to avoid truncation. However, if transactions API has pagination or the like, it would be preferable to make a transactions table paginate in the future.
Ticket
https://soramitsu.atlassian.net/browse/IWJ-8
Description
Create a transactions table.
The transactions table is implemented as a custom component
<transactions :walletId="...">
, which takes a wallet ID, fetch transactions data associated with the ID (dummy data for now) and render it. However, depending on the structure of wallet/transaction API, it might be better to directly pass the data as a prop.Wallet page scrolls to avoid truncation. However, if transactions API has pagination or the like, it would be preferable to make a transactions table paginate in the future.
How to check
yarn dev
to open the app.