How joeljohny/disasteraid works
Project type & purpose (from tree + minimal README)
DisasterAid is a full-stack web application with:
• Frontend: Angular SPA (frontend/)
• Backend: Node.js/Express API (backend/)
• Data access: Prisma (backend/src/config/prisma.js, backend/prisma.config.ts) connecting to a database (exact DB not shown in tree; Prisma implies a relational DB like Postgres/MySQL/SQLite).
Even though the root README is minimal, the code structure strongly indicates core features:
• User authentication (register/login, JWT-like flow) via authController, authRoutes, Angular auth.service, auth.guard, auth.interceptor.
• Skills management via skillsController, skillsRoutes.
• Reports endpoint(s) via reportsRoutes.
This is a classic “Angular SPA → REST API → DB” architecture.
Express App / Server Bootstrap
• src/app.js
Route Modules
• authRoutes.js
• skillsRoutes.js
• reportsRoutes.js
Each route module:
• exposes URL paths
• composes middleware chain
• delegates to controller functions
Middleware
• authMiddleware.js
• Validates token
• Attaches user context to request
Controllers
• authController.js
• skillsController.js
Controller as:
• “HTTP handlers” (input validation, orchestration)
• calls model/service/data layer
Models / Data Access
• userModel.js
• Prisma client wrapper: config/prisma.js
• DB config: config/db.js
Even if userModel.js is thin, show the intent:
• Domain model / persistence operations
• Prisma as the ORM/data mapper
Prisma
• Prisma as a distinct component (library) used by models/controllers:
• “Prisma Client → SQL DB”
Express App → mounts → Routes → (optional) authMiddleware → Controllers → Prisma Client → Database
Bootstrap + App Shell
• main.ts
• app/app.ts, app.html, app.scss
• app.config.ts (providers/configuration)
Routing
• app.routes.ts
• Routes to components (Login/Register/Dashboard)
Components
• login.component.ts
• register.component.ts
• dashboard.component.ts
Services
• auth.service.ts (HTTP calls, token handling)
Service as the primary client-side gateway to backend auth endpoints.
Interceptor
• auth.interceptor.ts
Guard
• auth.guard.ts
Frontend arrowing pattern:
Components → call → AuthService → uses → Angular HttpClient → passes through → AuthInterceptor → sends to → Express API
And for navigation:
Router → consults → AuthGuard → allows/denies → Dashboard route
Register/Login
• Angular Login/Register Component → AuthService → POST /auth/* → AuthController → DB (Prisma) → returns token/user
Authenticated API call
• Angular Dashboard → AuthService/other service → Interceptor adds token → GET /skills (or /reports) → AuthMiddleware verifies → SkillsController/Reports route → DB → returns data
Route protection
• Angular navigation to /dashboard → AuthGuard checks token/session → allow/redirect to login
Architectural patterns to explicitly encode
• Layered backend: Routes → Middleware → Controllers → Data Access (Prisma) → DB
• SPA + REST: Angular client is decoupled from backend via HTTP API
• Cross-cutting concerns:
• Frontend: Interceptor (auth header injection), Guard (authorization at routing)
• Backend: Auth middleware (authorization at API boundary)
“Don’t overthink it” decomposition checklist (specific to this project)
• Angular: App shell, Router, Login, Register, Dashboard, AuthService, AuthInterceptor, AuthGuard
• Express: app.js, authRoutes, skillsRoutes, reportsRoutes, authMiddleware, authController, skillsController
• Data: userModel, Prisma client, Database
• “Referenced by routes” / “Likely used for persistence” / “DB connector (legacy or supplementary)”