AgileWebs/waiter-floor-bff
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(waiter-floor-bff): align lifecycle assignment reads

Browse Source
This commit is contained in:
José René White Enciso 2026-03-31 19:59:32 -06:00
parent 95dc218f28
commit a347eebde4
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/api/waiter-floor-workflows.md
View File

@ -26,5 +26,6 @@ This BFF exposes execution-facing waiter workflows over REST while delegating or
## Notes ## Notes
- The update route currently reuses the operations order submission contract so waiter-floor can expose update semantics without introducing a new cross-repo dependency. - The update route currently reuses the operations order submission contract so waiter-floor can expose update semantics without introducing a new cross-repo dependency.
- Both order mutations project into the shared restaurant lifecycle owned by `operations-service`, which means kitchen and POS can observe the same order/check state after downstream stages are wired. - Both order mutations project into the shared restaurant lifecycle owned by `operations-service`, which means kitchen and POS can observe the same order/check state through the same runtime path.
- Assignment and recent-activity reads are already lifecycle-backed through `operations-service`, so this BFF does not need a separate summary-projection fallback for the Stage 49 propagation wave.
- Correlation IDs are preserved through Thalos session checks and operations-service calls. - Correlation IDs are preserved through Thalos session checks and operations-service calls.

5
tests/Waiter.Floor.Bff.Application.UnitTests/OperationsWaiterServiceClientTests.cs
View File

@ -15,7 +15,7 @@ public sealed class OperationsWaiterServiceClientTests
{ {
"contextId": "demo-context", "contextId": "demo-context",
"locationId": "restaurant-demo", "locationId": "restaurant-demo",
"summary": "2 active waiter assignments are currently visible.", "summary": "2 tables currently require floor attention.",
"assignments": [ "assignments": [
{ "waiterId": "service-pool", "tableId": "T-12", "status": "Preparing", "activeOrders": 2 } { "waiterId": "service-pool", "tableId": "T-12", "status": "Preparing", "activeOrders": 2 }
], ],
@ -42,7 +42,7 @@ public sealed class OperationsWaiterServiceClientTests
{ {
"contextId": "demo-context", "contextId": "demo-context",
"locationId": "restaurant-demo", "locationId": "restaurant-demo",
"summary": "2 active waiter assignments are currently visible.", "summary": "2 tables currently require floor attention.",
"assignments": [], "assignments": [],
"recentActivity": [ "recentActivity": [
"Order ORD-1003 was served at table T-21 and is ready for payment capture." "Order ORD-1003 was served at table T-21 and is ready for payment capture."
@ -55,6 +55,7 @@ public sealed class OperationsWaiterServiceClientTests
Assert.Equal("demo-context", response.ContextId); Assert.Equal("demo-context", response.ContextId);
Assert.Single(response.RecentActivity); Assert.Single(response.RecentActivity);
Assert.Contains("floor attention", response.Summary);
} }
[Fact] [Fact]