How kruthikb/eventz-planner-frontend works
Project type and purpose
• EventZ Planner is a full-stack MERN (MongoDB, Express, React, Node.js) event-management application.
• It provides user authentication, event CRUD operations, ticket booking, and QR-code ticket generation.
File structure
• Top level: public/ (static assets), src/ (React app), package.json, README.md
• src/components/ holds granular UI components (Add_Event, EventDetailsPage, Login, Signup, Navbar, etc.)
• src/context/AuthContext.js implements React Context for auth state (JWT, user roles)
• No backend code in this repo, but README refers to a separate backend folder with Express, Mongo models, controllers, routes.
README for additional insights
• Confirms MERN stack: React frontend, Node/Express API, MongoDB database
• Backend exposes REST endpoints for auth, events, bookings
• QR code generation and ticket PDF creation happen server-side
• JWT for stateless auth
Main components & interactions
a. Frontend SPA (React)
• Components talk to AuthContext to store/manage JWT and user info
• Uses fetch or axios to call API endpoints for login, signup, events, booking
b. Backend API (Node.js + Express)
• Auth routes: /api/auth/register, /api/auth/login → issues JWT
• Event routes: /api/events CRUD
• Booking routes: /api/bookings → issues ticket data + QR code
c. Database (MongoDB)
• Collections: users, events, bookings
d. External services
• QR code library or microservice (could be a Node module or external)
• Optional file storage (e.g., AWS S3 for event photos)
Interactions:
1. User → Frontend → AuthContext → Backend.auth → MongoDB
2. Frontend (with JWT header) → Backend.events → MongoDB
3. Frontend → Backend.bookings → MongoDB + QR code generator → returns ticket
Architectural patterns & design principles
• Separation of concerns: UI vs API vs Data store
• Stateless REST API with JWT-based auth
• React Context for global auth state
• Componentized UI (atomic components, pages)
• Potential MVC on backend (models/controllers/routes)
Detailed capture of essential elements
• Lifecycle of a request: User clicks “Book Ticket” → React Book component dispatches fetch → Express booking route verifies JWT → stores booking in MongoDB → generates QR code → returns ticket JSON → React displays confirmation
• Authentication flow: React Login → API validates credentials → issues JWT → stored in local storage → used by ProtectedRoute component to guard routes
• React Context: all components that need auth state consume AuthContext