How saksoft-training/task-management-system works
Project type and purpose
• This is a single-page application (SPA) built with Angular (v20.3.8) for managing tasks, projects, dashboards, and user accounts. It provides features like activity feeds, charts, statistics, project CRUD, task boards, user authentication, and shared UI elements.
Key architectural components (based on the file structure)
a. App Module (src/app/app.ts, app.module.ts)
b. Core Module (src/app/core)
– Authentication adapters, HTTP interceptors, global configuration (app.config.ts), routing (app.routes.ts)
c. Feature Modules (src/app/features)
– Dashboard
– Display-Statistics-and-Overview
– Project-Management
– Task-Management
– User-Account-Management
d. Shared Module (src/app/shared)
– Reusable components (dialogs, loading spinner, header/footer), pipes, directives, constants, services (storage), utilities
e. Contracts & Types (src/app/contracts & src/types)
– Interface definitions for API payloads and domain models
f. Assets & Styling
g. Build & Configuration
– Angular CLI config (angular.json), tsconfig files, environment (vercel.json)
External dependencies
• REST-style backend (not present here) accessed through services in each feature module
• Third-party libraries specified in package.json (e.g., RxJS, Angular Material or similar)
Relationships and interactions
• App Module bootstraps the SPA, imports Core, Shared, and Feature modules, and configures root router
• Core Module provides singleton services (AuthService, AuthInterceptor) injected across features
• Feature Modules group related components and services; each module defines its own routing and injects shared/core services
• Shared Module exports UI building blocks used by all feature modules
• HTTP Requests flow from feature services → Core/AuthInterceptor → backend API → data models (Contracts & Types) → components
• State Management: either local component state or a store under src/app/store (if implemented)
Architectural patterns & design principles
• Modularization: features are isolated into lazy-loaded Angular modules
• Separation of Concerns: UI (components) vs. business logic (services) vs. data contracts (interfaces/types)
• Dependency Injection: Angular DI for services, interceptors, and configuration
• Reusable UI: Shared module for common UI primitives
• Routing: route definitions in app.routes.ts, feature-specific routing within modules