How tinhne/capstons2 works
Project Type and Purpose
• This project is clearly a full-stack application with both a backend (Java/Spring Boot) and a frontend (React/TypeScript) component.
• The backend appears to handle functionalities around disease prediction, authentication, chat, and role/permission management (as seen from directories like “controllers” for Disease, Symptom, and Authentication; “models” for Disease, Symptom, and User; and “services” that encapsulate business logic).
• The frontend organizes features into sections such as authentication, administration (admin features), chat, and users, using Redux for state management and a component-driven design.
Analyzing the File Structure
• Backend:
• The “backend” directory follows a clear layered (MVC) architecture: configuration, controllers, DTOs, exceptions, mappers, models, repositories, and services (with separate implementation packages).
• Standard Spring Boot structures are present (e.g., Application class in BackendApplication.java) together with security configurations (JWT-based authentication).
• A build file (pom.xml) and Maven scripts ensure that it’s managed as a Java project.
• Frontend:
• The “frontend” directory is a typical React project enhanced with TypeScript, Redux for state management, and organized by features (e.g., “auth”, “chat”, “admin”, “users”), along with shared resources (contexts, hooks, utils, layouts).
• It contains build and configuration files (e.g., vite.config.ts, tailwind.config.js) which indicate modern tooling for a web application.