How kittapat-deein/w13-clinicapp-66025560 works
This repository is a whiskey reservation app presented as a clinic-app starter: the sampled UI and API use whiskey and order terminology, while the README describes the Azure clinic deployment and legacy appointment endpoints. The user workflow is to browse and select a whiskey, submit reservation details, then review or cancel an order; the API reads and writes SQL data. Some UI request code was not excerpted, so the frontend-to-API relationship follows the README’s proxy/API description rather than a sampled call.
Main entry points: index.js Express API · db.js SQL pool · App.jsx Reservation UI · main.jsx React entry
Components 12
Web app
- React entry
web/src/main.jsx - Reservation UI
web/src/App.jsx
Reservation API
- Express API
server/index.js - Whiskey catalog
server/index.js - Order history
server/index.js - Create reservation
server/index.js - Cancel reservation
server/index.js
SQL persistence
- SQL pool
server/db.js - Azure SQL
db/schema.sql - Schema and seed data
db/seed-data.sql
Other components
- Visitor
- Azure SQL service
Connections 15
- Visitor → React entry: opens app
README.md - React entry → Reservation UI: renders
web/src/main.jsx - Visitor → Reservation UI: uses
web/src/App.jsx - Reservation UI → Express API: calls API
README.md - Express API → Whiskey catalog: routes catalog
server/index.js - Express API → Order history: routes history
server/index.js - Express API → Create reservation: routes booking
server/index.js - Express API → Cancel reservation: routes cancellation
server/index.js - Express API → SQL pool: gets pool
server/index.js - Whiskey catalog → SQL pool: queries
server/index.js - Order history → SQL pool: queries
server/index.js - Create reservation → SQL pool: checks and inserts
server/index.js - Cancel reservation → SQL pool: deletes
server/index.js - SQL pool → Azure SQL service: connects
server/db.js - Schema and seed data → Azure SQL: initializes
README.md