How untolders/my_airbnb works
Project type and purpose
• This is a full-stack web application—an Airbnb clone—built with a ReactJS single-page application (SPA) front end and a Spring Boot back end.
• Purpose: allow Guests to search and book listings, Hosts to create and manage listings and messages, and Admins to oversee users, listings, reviews, and extract application data.
File structure
• Top-level split:
• api-hits/ – sample API payloads
• back-end/AirBnB/ – Spring Boot project (controllers, services, repositories, models, security, converters, util/recommender)
• front-end/airbnb/ – React app (components organized by user role and feature, services, routes, helpers, context)
• Backend layering:
• Controllers (REST endpoints)
• Converters (DTO ↔ entity)
• Services (business logic + recommendation engine)
• Repositories (Spring Data JPA)
• Util (JWT, Helpers, Recommender algorithms)
• Frontend structure:
• Pages & components by role (Admin, Host, Guest, general listings)
• _services for API calls
• _helpers for auth headers & history
• Routes define protected routes per role
• Context for auth state
README for additional insights
• Build/run instructions for back end (Gradle) and front end (npm).
• Screenshots reveal core UI flows: home, login/register, profile, search, role-based dashboards.
Detail without over-splitting
• Every major layer and sub-module essential to understanding data flow and security.
• Avoid drilling into every single Java package; group similar components (all controllers together, all repositories together).
• Document the JWT authentication flow and role-based routing on the front end.