HSLG Media

TableOrdering.js

TableOrdering.js

Source file: packages/app-ui/src/legacy/TableOrdering.js

Module: package-app-ui

Size: 257 lines

SHA-256: 6973d88cc13711503467e42fccfc1abe3b10ccdac9fda317aa9a6de6c3ed9772

Responsibility

Owns the shared customer screens, interactions, styles and approved brand assets.

Declared entry points

  • ASSET — source line 8.
  • screen — source line 9.
  • root — source line 10.
  • sessions — source line 11.
  • activeVenue — source line 12.
  • receiptSequence — source line 13.
  • baseRender — source line 14.
  • baseGo — source line 15.
  • symbols — source line 16.
  • svg — source line 39.
  • cents — source line 40.
  • pounds — source line 41.
  • state — source line 42.
  • count — source line 43.
  • totalCents — source line 44.
  • categories — source line 45.
  • meta — source line 46.
  • syncVenue — source line 52.
  • masthead — source line 58.
  • v — source line 59.
  • steps — source line 62.
  • entry — source line 65.
  • confirmTable — source line 75.
  • input — source line 76.

Imports and dependencies

No direct import declarations detected in this file.

Behaviour and audit locations

Review control flow and returned values in the named source file; no special integration marker was detected.

Existing ordering interface

The legacy shared code handles table-first interaction, category/menu view, item selection and the basket's slide-up control. Venue/table state must stay consistent while the customer changes items and navigates between panels. The browser presenter supplies example catalogue and success responses; native services have no live catalogue yet. Before enabling checkout, connect a real server-priced menu, SQLite outbox and payment reconciliation rather than treating UI calculations as final prices. This is a priority candidate for typed component extraction.

Relationship to the system

This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.

Change verification

Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.