monaiuu
commented
1 year ago Edge Cases:
-
Incomplete Transactions: The component should handle transactions that are incomplete due to connectivity issues, insufficient funds, or other reasons.
-
Long-Pending Transactions: The system should have a way to deal with transactions that are stuck in a pending state for a prolonged time.
-
Failed Transactions: Proper error handling and messaging should be implemented for failed transactions.
Objective:
To design and implement a Transaction History Component that provides users with comprehensive, accessible and relevant details about their transactions on Hubble. This component will be a part of the user's account dashboard.
Features:
- Clear Transaction History: Users should be able to erase their displayed transaction history. Caution: Users should be made aware that this does not delete their transactions from the blockchain.
- Export Transaction History: Users should be able to export their transaction history in standard formats like CSV, JSON or PDF.
- View the Spend Note(s) associated with transactions: Each transaction should be linked to its corresponding spend note(s). Users should be able to click on a transaction and see these spend note details in a separate, detailed view.
- Transaction Type: Users should be able to see the type of transaction (deposit, transfer, withdrawal) next to each transaction entry.
- View transaction on the block explorer: Each transaction should have a link to its record on the respective blockchain's block explorer.
- View the Recipient Address: Users should be able to see the recipient's address for each transaction.
- View status of ongoing transactions: Each transaction should display its current status (e.g., pending, confirmed, failed). If a transaction fails, an error message should be displayed explaining the reason for the failure.