How jhosefrea/gui-purchase-invoice-management works
Project type and purpose
• This is a full‑stack invoice‑management system. The repository you see is the Angular front‑end (“PROYECTO FRONT‑END”) that consumes a FastAPI back‑end.
• It uses Angular 19+, TailwindCSS, TypeScript, SOLID principles, clean‑code and a modular architecture.
File structure
• Top‑level files: angular.json, package.json, tsconfig*.json, tailwind.config.js, .env.example – standard Angular + Tailwind setup.
• src/app contains AppModule plus feature modules (dashboard, invoices, users, reports, login, welcome).
• src/app/services holds HTTP service classes (FetchApiDataService, FetchApiUserService, FetchApiReportService) and a ToasterService.
• src/shared contains reusable components (header, layout, sidebar-nav), utilities (enums, modal, models).
• public and src/assets contain static assets and global styles (Tailwind).
README for additional insights
• Core tech: Angular front‑end served via ng serve; FastAPI back‑end on Uvicorn at port 8002.
• Deploy/Run: environment variables (.env.example → environment.ts), Node.js 20+, Angular CLI, Python/FastAPI.
a. Main components:
– Browser/Client UI
– Angular App shell (AppModule)
– Feature Modules:
· DashboardModule
· InvoiceModule (details, edit, view)
· UsersModule (list, create, edit)
· ReportsModule
· AuthModule (login, welcome)
– SharedModule (header, layout, sidebar‑nav, modal)
– Service Layer (FetchApi… services + ToasterService)
– HTTP Client (Angular HttpClient)
– External Service: FastAPI REST API
– Database (e.g., PostgreSQL/MySQL behind FastAPI)
– Environment/config (environment.ts / .env)
b. Relationships and interactions:
– UI Components call injected Services → Services issue HTTP requests via HttpClient → FastAPI endpoints → Database → JSON responses → back to Services → UI Components.
– AuthModule handles login, stores tokens in environment or localStorage.
– SharedModule components provide consistent header/sidebar across all feature modules.
– TailwindCSS provides styling at the assets/styles layer.
c. Architectural patterns & design principles:
– Modular architecture: one feature per module, with AppRoutes managing lazy loading.
– SOLID / Clean Code: single‑responsibility services, reusable shared components, clear folder structure.
– Separation of concerns: UI vs. data vs. routing vs. styling (Tailwind).
– Dependency injection: Angular DI for services and shared components.
d. Key technologies & frameworks:
– Angular (Components, Modules, HttpClient, Routing)
– TypeScript, RxJS (observables)
– TailwindCSS for utility‑first styling
– FastAPI + Uvicorn on port 8002 (Python)
– RESTful JSON over HTTP
– Node.js / npm for build chain