AgileWebs/waiter-floor-web
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
a0dc0a29ed
waiter-floor-web/docs/architecture/frontend-boundary.md
José René White Enciso a0dc0a29ed feat(waiter-floor-web): deepen floor workflow experience
2026-03-31 16:50:12 -06:00

1.3 KiB
Raw Blame History

Frontend Boundary

  • This repository hosts a React edge application for a single BFF.
  • Frontend data access flows through src/api/* adapter modules.
  • The UI does not access DAL or internal services directly.
  • Route shell uses Ant Design layout/menu and keeps business views behind session checks.
  • Unauthenticated users are redirected to the central auth host OIDC start endpoint.
  • Session-expired responses are treated as an auth boundary concern and trigger revalidation before the UI prompts for login again.

Runtime Base URLs

  • API_BASE_URL for business BFF calls.
  • THALOS_AUTH_BASE_URL for session login/refresh/logout/me.
  • THALOS_DEFAULT_RETURN_URL for safe callback fallback.
  • THALOS_DEFAULT_TENANT_ID for OIDC tenant context defaults.

Protected Workflow Endpoints

  • GET /api/waiter/floor/assignments?contextId=...
  • GET /api/waiter/floor/activity?contextId=...
  • POST /api/waiter/floor/orders
  • PUT /api/waiter/floor/orders/{orderId}

UI Workflow Coverage

  • Waiter assignment snapshot with location metadata and active-order counts
  • Recent waiter activity history feed
  • Floor order submission and order update workflows
  • Session-expired handling with reauthentication guidance
  • Protected route shell for assignments, order actions, and session inspection