Skip to content

Conversation

@egarciajulia
Copy link
Owner

What I Did

This PR fixes the transaction display bug by filtering transactions on the frontend to only show relevant entries. I've also implemented server-side pagination for better performance.

How to Test

  1. Checkout this branch.
  2. Run docker-compose up --build.
  3. Navigate to the frontend at http://localhost:3000.
  4. Observe that only relevant transactions are displayed.
  5. Verify that pagination controls are now active and functional.

Architectural Decision Record (ADR)

To address the display bug, I decided to handle filtering directly in the frontend component. This approach simplifies the backend and leverages the client's processing power for a snappier user experience. For pagination, I added a new GET parameter page and page_size to the existing /api/v1/transactions/ endpoint, and updated the frontend to send these parameters.

AI Usage Summary

I used AI tools for minor code refactoring and to generate some boilerplate for the frontend pagination component.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants