Type of feature
🍕 Feature
Current behavior
The app currently loads the full transaction history, which can eventually amount to a high memory usage, once the user starts accumulating transactions and eventually lead to a server crash due to memory usage limits.
Suggested solution
Implement pagination/sorting (together with filtering) with Spring Data JPA to main page.
Docs and suggested readings:
Additional context
No response
Code of Conduct
Contributing Docs
Type of feature
🍕 Feature
Current behavior
The app currently loads the full transaction history, which can eventually amount to a high memory usage, once the user starts accumulating transactions and eventually lead to a server crash due to memory usage limits.
Suggested solution
Implement pagination/sorting (together with filtering) with Spring Data JPA to main page.
Docs and suggested readings:
Additional context
No response
Code of Conduct
Contributing Docs