How chaimae-chakir/amortization works
Project type and purpose
• This is a full-stack web application (“Loan Amortization Table Generator”) consisting of:
• An Angular (TypeScript) frontend under report-front/ that provides a UI for entering loan parameters and downloading PDFs.
• A Spring Boot (Java/Maven) backend under report/ that exposes REST endpoints, computes amortization schedules, uses JasperReports to render the PDF, and (optionally) persists report metadata.
File structure
• Top-level directories:
• report-front/ – Angular CLI project (src/app/components, models, services, shared modules, configuration files).
• report/ – Spring Boot project (src/main/java for controllers, services, repositories, config, exception handlers; src/main/resources for application.properties and JRXML templates; src/test for unit tests).
• Build/deployment artifacts:
• Angular uses Vite under the .angular cache, package.json, tsconfig.
• Backend uses Maven wrapper (mvnw, pom.xml).
• Key patterns:
• Frontend follows an MVC-ish structure (components + services + models + routing).
• Backend follows layered architecture (Controller → Service → Repository + external JasperReports engine).
README
• Confirms Angular + Spring Boot, JasperReports for PDF generation, user-driven report download.
Elements
• Clear labels: e.g., “Angular App”, “ReportController”, “AmortizationCalculator”, “JasperReports Engine”, “Database”.
• From Browser → Angular Service → REST API → Controller → Service → JasperReports/Repository → back up to Browser.
• Blue rectangles for frontend modules/components
• Green rectangles for backend layers
• Protocols (HTTP/JSON), file types (JRXML → PDF), and build tools (npm, Maven) if space permits.
Detail
• Distinct module (e.g., amortization-table component, shared module, WebConfig, GlobalExceptionHandler).
• How JRXML in src/main/resources/reports flows into the reporting engine.
• Don’t oversimplify: even small services or exception handlers should appear if they play a role in the flow.