How hendragunadie/sakurasushi works
SushiWebAPI is a restaurant point-of-sale API for staff workflows: open a table transaction, manage its cart and orders, track item preparation, and take payment. Controllers use SushiContext to read and persist the workflow’s state; the model layer represents menu, table, transaction, cart, and order data. The supplied excerpts establish cart and transaction persistence and SQL Server configuration. Auth and menu endpoints appear in the source index, but their implementation details were not excerpted, so their specific behavior and links are not asserted.
Main entry points: SushiContext.cs EF data context · CartController.cs Cart endpoints · TransactionController.cs Transaction endpoints · Order.cs Order
Components 17
API endpoints
- Authentication
SushiWebAPI/Controller/AuthController.cs - Menu endpoints
SushiWebAPI/Controller/ItemController.cs - Cart endpoints
SushiWebAPI/Controller/CartController.cs - Transaction endpoints
SushiWebAPI/Controller/TransactionController.cs - Response helpers
SushiWebAPI/Helper.cs
Sales workflow
- Cart item
SushiWebAPI/Models/CartItem.cs - Transaction
SushiWebAPI/Models/Transaction.cs - Order
SushiWebAPI/Models/Order.cs - Order item
SushiWebAPI/Models/OrderItem.cs - Dining table
SushiWebAPI/Models/Table.cs
Menu and identity
- Menu item
SushiWebAPI/Models/Item.cs - Menu category
SushiWebAPI/Models/Category.cs - Staff user
SushiWebAPI/Models/User.cs
Persistence
- EF data context
SushiWebAPI/Data/SushiContext.cs - SQL Server
Other components
- Restaurant staff
- API client
Connections 25
- Restaurant staff → Authentication: requests access
- API client → Menu endpoints: requests menu
- API client → Cart endpoints: manages cart
- Restaurant staff → Transaction endpoints: handles transactions
- Cart endpoints → EF data context: reads and writes
SushiWebAPI/Controller/CartController.cs - Transaction endpoints → EF data context: reads and writes
SushiWebAPI/Controller/TransactionController.cs - EF data context → SQL Server: configures connection
SushiWebAPI/Data/SushiContext.cs - EF data context → Cart item: maps
SushiWebAPI/Data/SushiContext.cs - EF data context → Menu category: maps
SushiWebAPI/Data/SushiContext.cs - EF data context → Menu item: maps
SushiWebAPI/Data/SushiContext.cs - EF data context → Order: maps
SushiWebAPI/Data/SushiContext.cs - EF data context → Order item: maps
SushiWebAPI/Data/SushiContext.cs - EF data context → Dining table: maps
SushiWebAPI/Data/SushiContext.cs - EF data context → Transaction: maps
SushiWebAPI/Data/SushiContext.cs - EF data context → Staff user: maps
SushiWebAPI/Data/SushiContext.cs - Cart endpoints → Response helpers: formats responses
SushiWebAPI/Controller/CartController.cs - Transaction endpoints → Response helpers: formats responses
SushiWebAPI/Controller/TransactionController.cs - Cart endpoints → Menu item: looks up menu item
SushiWebAPI/Controller/CartController.cs - Cart endpoints → Transaction: looks up transaction
SushiWebAPI/Controller/CartController.cs - Cart endpoints → Order: creates order
SushiWebAPI/Controller/CartController.cs - Cart endpoints → Order item: creates order line
SushiWebAPI/Controller/CartController.cs - Transaction endpoints → Dining table: looks up table
SushiWebAPI/Controller/TransactionController.cs - Transaction endpoints → Order: reads order totals
SushiWebAPI/Controller/TransactionController.cs - Transaction endpoints → Order item: updates status
SushiWebAPI/Controller/TransactionController.cs - Transaction endpoints → Staff user: reads staff claim
SushiWebAPI/Controller/TransactionController.cs