How siddhantpatni0407/angular-tracker-manager-ui works
Project type and purpose
• This is a full‑stack work‑item‑tracking application. The provided repo contains the Angular front‑end (“angular‑tracker‑manager‑ui”), and the README indicates a Spring Boot/PostgreSQL back‑end (not in this tree). It supports user auth (register/login), an admin panel, and multiple “trackers” (vehicles, credentials, financial, medical, stock‑market).
File structure
• Top‑level files: Angular configuration (angular.json, tsconfig*.json), package.json, README.
• src/app:
• app.module.ts, routing modules and config – the root Angular module and router.
• components/…: feature folders by domain (auth, admin‑panel, credential‑tracker, financial‑tracker, medical‑tracker, stock‑market‑tracker, vehicle‑tracker, dashboard, update‑user). Each contains its component(s), nested subcomponents for add/view/update operations.
• services/: Angular services for API calls (auth.service.ts, vehicle.service.ts, etc.).
• models/: TypeScript interfaces for request/response payloads.
• guards/: route guard for protected routes.
• constants/: endpoint constants.
• Public/assets and static files under src/index.html, styles.css.
• No back‑end code here, but README specifies a Spring Boot service with PostgreSQL and Liquibase.
README for additional insights
• Front‑end: Angular + Bootstrap.
• Back‑end: Spring Boot (Java 21), PostgreSQL + Liquibase, Gradle.
• Typical commands and project structure overview.
a. Main components
• Front‑end Angular client
• Modules: AuthModule, AdminModule, TrackerModules (Vehicle, Credential, Financial, Medical, StockMarket), SharedModule (services, models, guards, constants), AppRouter
• Back‑end Spring Boot API
• Controllers, Services, Repositories
• Database: PostgreSQL
• Migration tool: Liquibase
• External libraries: jsPDF/xlsx for export
b. Relationships & interactions
• Angular → HTTP(S) REST calls → Spring Boot controllers
• Controllers → service layer → repository layer → PostgreSQL
• Liquibase executes before application start to manage schema
• Angular route guard checks JWT/local‑storage token issued by back‑end
• Export libraries in Angular call browser APIs to generate PDFs/Excel
c. Architectural patterns / design principles
• Front‑end: Component‑based architecture, feature modules, Router for navigation, service layer for API integration, guard for route protection
• Back‑end: Layered architecture (Controller-Service-Repository), RESTful API, database migrations with Liquibase
• Separation of concerns between UI, API, data persistence
d. Key technologies
• Angular, TypeScript, Bootstrap, jsPDF, XLSX
• Spring Boot, Java, Gradle, PostgreSQL, Liquibase
Detailed capture of essential elements
• Route guard intercepting navigation
• Under each Tracker feature, list subcomponents (Add / View / Manage)
• On back‑end side, indicate typical CRUD endpoints for each tracker type
• Export feature: Angular → jsPDF/xlsx library → file download