How plascore/pwcs-calorie-tracker works
This is a school-menu browser app with a calorie counter. A user selects a date; the client requests that day’s menu through a serverless proxy, which forwards the GraphQL request to the nutrition service. The client filters and displays menu items, and users can add or remove items to update a local calorie total. The available excerpts show the client and proxy behavior; no README or HTML excerpt was provided, so page structure and other capabilities are not inferred.
Main entry points: script.js Menu client · menu.js Menu API proxy
Components 5
Browser app
- Menu client
script.js - Calorie counter
script.js
Menu integration
- Menu API proxy
functions/api/menu.js - Nutrition GraphQL API
Other components
- User
Connections 7
- User → Menu client: selects date
script.js - Menu client → Menu API proxy: requests menu
script.js - Menu API proxy → Nutrition GraphQL API: forwards query
functions/api/menu.js - Nutrition GraphQL API → Menu API proxy: returns response
functions/api/menu.js - Menu API proxy → Menu client: returns menu
script.js - User → Calorie counter: adds or removes
script.js - Menu client → Calorie counter: adds item
script.js