Problem
1. TransactionHistory does not support filtering by status (Success/Failed) — the list shows all transactions mixed. A status filter (All / Success / Failed) in the card header would help users find failed transactions quickly.
2. TransactionHistory does not support date range filtering — there is no way to narrow the history to a specific date range. Adding start/end date <Input type="date"> fields would let users export or review activity for a period.
3. TransactionHistory row clicks have no action — clicking a row does nothing. Rows should be linkable to Stellar Expert for the active network.
Solution
- Add status filter toggle buttons (All / Success / Failed) in the card header, passing the filter to
getHistory.
- Add optional
startDate/endDate ISO string props to TransactionHistory; pass them to getHistory when set.
- Wrap each
TxRow in an <a href> pointing to the correct Stellar Expert URL for the transaction hash.
Acceptance Criteria
Note for Contributors: Write a clear PR description. Include a screenshot of the filter controls and a clicked-row navigation to Stellar Expert.
Problem
1.
TransactionHistorydoes not support filtering by status (Success/Failed) — the list shows all transactions mixed. A status filter (All / Success / Failed) in the card header would help users find failed transactions quickly.2.
TransactionHistorydoes not support date range filtering — there is no way to narrow the history to a specific date range. Adding start/end date<Input type="date">fields would let users export or review activity for a period.3.
TransactionHistoryrow clicks have no action — clicking a row does nothing. Rows should be linkable to Stellar Expert for the active network.Solution
getHistory.startDate/endDateISO string props toTransactionHistory; pass them togetHistorywhen set.TxRowin an<a href>pointing to the correct Stellar Expert URL for the transaction hash.Acceptance Criteria
startDate/endDateprops filter the API callnpm run buildpasses