How anitamavani/contactmanager works
Project Type & Purpose
• Full-stack web application: React + TypeScript frontend + Material-UI, backed by Node.js + Express REST API, persisting data in MySQL.
• Purpose: Allow users to register/login (JWT), then perform CRUD operations on contacts.
Main Components
A. Client Layer (Frontend)
• Browser/app running React (TypeScript)
• Uses React Router for navigation, Material-UI for styling
• Pages: Home, About (public), Auth (register/login), Contact (CRUD, protected)
• Authentication context + custom hooks (useAuth, useForm) manage state & API calls
B. API Layer (Backend)
• Express.js application
• Routes:
• /api/auth/* (userRoutes.js)
• /api/contacts/* (contactRoutes.js)
• Middleware:
• CORS & body-parser (global)
• authMiddleware.js (JWT verification)
• contactValidation.js (request payload validation)
• errorHandler.js (centralized error response)
• Controllers invoke business logic:
• userController.js → register/login & JWT generation
• contactController.js → CRUD logic
C. Data Layer
• Models define queries/interactions with MySQL (via mysql2 or similar)
• userModel.js
• contactModel.js
• Configuration: db.js reads connection settings from my.cnf or env
D. External Services
• MySQL database instance
• JWT Signing (using secret from .env)
Relationships & Data Flow
1) User interacts with React UI → triggers a page or API action.
2) Frontend uses fetch/axios to call Express endpoints under /api/auth or /api/contacts.
3) On auth routes: userController
→ generates JWT → returned to frontend → stored in context/localStorage
4) For protected /contacts calls: frontend sends JWT in Authorization header → authMiddleware verifies → passes control to contactController.
5) Controllers call model layer → execute SQL queries → return results → middleware/formatted response → frontend.
Architectural Patterns & Principles
• MVC-inspired within the backend: Routes → Middleware → Controllers → Models → DB
• Separation of Concerns:
• Frontend UI vs. business logic (controllers) vs. data access (models)
• Centralized middleware for cross-cutting concerns (auth, validation, error handling)
• Stateless API: uses JWT tokens
• Single Monolithic Service (no microservices) but clearly separated folders