How dt0072/capstone-project works
Project type and purpose
• This is a single‐page application (SPA) built with Angular (v15), intended to run in the browser and be hosted on Firebase.
• The README indicates it uses the Angular CLI, runs locally via ng serve, builds to dist/, and is set up for Firebase deployment (.firebaserc, firebase.json).
File structure
• Top‐level config files:
• angular.json, tsconfig*.json: Angular build & compile configuration
• firebase.json, .firebaserc: Firebase hosting/deploy settings
• package.json / package‐lock.json: dependencies (Angular, Firebase SDK, etc.)
• src/app:
• A large collection of feature modules/components (e.g., attractions, eateries, bookings, cart, admin, user dashboards, login/register, searchbar, etc.)
• Shared services under src/app/shared (AuthenticationService, DataService)
• Domain models under src/app/model (att-data.ts, eat-data.ts, etc.)
• Business‐logic services at top‐level of src/app (booking.service.ts, cart.service.ts, searchbar.service.ts, plus an InMemoryDataService for local mock)
• app-routing.module.ts: defines client‐side routes
• app.module.ts: bootstraps the root NgModule
• src/environments: environment.ts / environment.development.ts for injecting Firebase config and other environment variables.
• assets: static assets (images, etc.).
README for additional insights
• The Angular CLI setup implies a classic component‐service layered front‐end.
Be detailed & capture essential elements
• Feature modules or group them logically (e.g., “Booking features,” “Cart features,” “Admin features”)
• Router module connecting components to URL paths