How truongthuyquangnhat/angular-erm works
Project type and purpose
• This is a frontend-only Single Page Application (SPA) built with Angular (v15), named “AngularERM”.
• Purpose: Manage “nhân viên” (employees)—display lists, pagination, CRUD via dialogs, using models, services, and routing.
File structure
• Top-level Angular CLI files: angular.json, package.json, tsconfig*.json.
• src/app: the root AppModule (app.module.ts), AppComponent, and AppRoutingModule.
• src/app/models: TypeScript model definitions (ChucDanhModel, ChucVuModel, PhongBanModel, TempModel).
• src/app/nhanvien: feature folder containing NhanVienComponent, a NhanVienModule, NhanVienService, and its interface.
• src/app/nhanvien/pagenhanvien: a nested feature module for pagination (PagenhanvienComponent, service, module).
• src/assets: static assets folder.
• No backend code present; services likely call an external REST API.
README
• Confirms Angular CLI scaffolding.
• No backend details—implies services target external endpoints.
• Standard build, serve, test commands.
Main components & interactions
a. Components/Modules
• Browser/Client
• AppModule
– AppComponent (root view)
– AppRoutingModule (defines routes to feature modules)
• NhanVienModule
– NhanVienComponent (CRUD UI + delete dialog)
– NhanVienService (HTTP calls for employees)
• PagenhanvienModule
– PagenhanvienComponent (pagination UI)
– PagenhanvienService (HTTP calls for paged data)
• Models (data contracts for HTTP payloads)
• Assets & Styles
b. External Services
• REST API server (external), serving employee data endpoints
c. Data flow
– User interacts with Component → calls corresponding Service → Service issues HTTP to API → API responds → Service returns Observable<Model> → Component renders data.
d. Architectural patterns
• Feature modules (NgModule) for separation of concerns
• Service-based data access (Dependency Injection)
• Router lazy-loading (if configured)
• Model classes as interfaces for strong typing