Problem
The History page (src/pages/History.tsx) fetches ALL transactions at once with no pagination. As the transaction count grows, this will cause slow page loads and excessive API responses.
User impact: Users with many transactions experience slow page loads. The API may return truncated results.
Root Cause
The fetchTransactions call in history.service.ts has no pagination parameters. The API, controller, and UI all lack pagination support.
What To Build
- Add
page and limit parameters to history.service.ts:fetchTransactions()
- Add pagination controls to the History page (prev/next buttons or page numbers)
- Show "Page X of Y" indicator
- Add loading state while fetching each page
- Add empty state when no transactions exist
Files To Touch
src/pages/History.tsx — add pagination UIsrc/services/history.service.ts — add pagination params
Acceptance Criteria
Mandatory Checks
Problem
The History page (src/pages/History.tsx) fetches ALL transactions at once with no pagination. As the transaction count grows, this will cause slow page loads and excessive API responses.
User impact: Users with many transactions experience slow page loads. The API may return truncated results.
Root Cause
The
fetchTransactionscall in history.service.ts has no pagination parameters. The API, controller, and UI all lack pagination support.What To Build
pageandlimitparameters tohistory.service.ts:fetchTransactions()Files To Touch
src/pages/History.tsx— add pagination UIsrc/services/history.service.ts— add pagination paramsAcceptance Criteria
Mandatory Checks