How pierregoupil13/spending works
This is a small Spring Boot spending tracker. Users can open an entry form, save a categorized spending record, view all records, and filter records by date range. The controller owns those request flows, delegates persistence to a Spring Data JPA repository, and returns server-rendered templates. The entity and category enum define the stored spending data and its classification. Template contents and database configuration were not sampled, so the form and storage wiring are shown only where supported by the controller and repository declarations.
Main entry points: SpendingController.java Spending controller · SpendingRepository.java Spending repository · add-spending.html Add spending view · list-spending.html Spending list view
Components 8
Web interaction
- Spending controller
src/main/java/app/spending/spending/Controller/SpendingController.java - Add spending view
src/main/resources/templates/add-spending.html - Spending list view
src/main/resources/templates/list-spending.html
Spending domain
- Spending record
src/main/java/app/spending/spending/Entity/Spending.java - Spending categories
src/main/java/app/spending/spending/Entity/Category.java
Persistence
- Spending repository
src/main/java/app/spending/spending/Repository/SpendingRepository.java - JPA database
Other components
- User
Connections 8
- User → Spending controller: sends requests
- Spending controller → Add spending view: renders form
- Spending controller → Spending list view: renders results
- Spending controller → Spending categories: loads categories
- Spending controller → Spending repository: saves spending
- Spending controller → Spending repository: reads spending
- Spending repository → JPA database: persists records
- Spending controller → Spending record: binds record