writeonce/docs/examples/site/CODE-LOGIC.md
shoney.arickathil f465ad5751 feat(lang+wo-html): raw text literals, component layer, MVC samples
- lexer: backtick raw text literal — content verbatim, no escape
  processing, common source margin removed at lex time; `${ }` raw and
  `{{ }}` auto-escaping holes
- `{{ e }}` desugars to `esc(${e})` in parser.ml — a Call on the `esc`
  in scope, so types/owner/emit/.wob/VM are untouched
- WO-E004 unterminated raw literal; WO-E005 newline inside "..." —
  closes a hole where a missing quote silently ate the rest of the file
- wo-html: `Component` interface, `render_all`, `Layout`, README
- framework: `ok_html` joins ok_text/ok_json in http/types.wo
- site + shop restructured to one-feature-one-module MVC (view +
  controller per directory, model at the root, bootstrap-only main)
- removed the filler `pad: Int` convention — verified unnecessary for
  plain classes, interface dispatch, containers and actors
- corrected recorded claims: gap #1 blocks neither the build nor the
  layout; a class crosses module lines, only a free fn is scoped
- docs/guides/language-surface.md — the full grammar inventory
- story 37 landed and moved to done/

Gates: oop-accept MET, oop-e2e 116/0, woc-test 556/0, site 11/0,
web-app 46/0, fibers 10/0, db-actor 8/0

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-25 03:58:41 +02:00

4.9 KiB

site — how it is put together

Written 2026-08-23 with the sample's landing; restructured 2026-08-25 onto the program template's MVC layout (docs/examples/shop), so the two samples now read the same way.

The layout

file layer what it owns
types.wo MODEL the Chapter @table, the ChapterLink projection, Chapters.links(), and seed_if_empty()
content.wo MODEL (content) the nine chapter bodies as fragment-returning functions, plus seed_chapters()
layout/app.wo VIEW (chrome) AppShell — the component that fills wo-html's Layout — the two named widths, and html_error
layout/header.wo, layout/footer.wo VIEW (chrome) the shared nav bar and footer
home/view.wo VIEW HomePage and the homepage's code showcase
home/controller.wo CONTROLLER Home — the / handler
chapter/view.wo VIEW ChapterNav, ChapterPage
chapter/controller.wo CONTROLLER ShowChapter — the /ch/:slug handler
admin/controller.wo CONTROLLER AdminEdit — bearer-gated edit, answers a redirect (no view: it redirects)
health/controller.wo CONTROLLER Health — the liveness probe (no view: it answers text)
main.wo BOOTSTRAP seed, routes, serve. Nothing else
wo.toml — the two [deps]: framework (serving) and html (markup)

One feature = one directory = one module, holding that feature's view and its controller together. A module sees its own declarations plus what it uses, so home/ reaching the chapter nav has to say use chapter.

The model stays at the root and is reachable from everywhere: a CLASS crosses module lines without being exported, and only a free fn is module-scoped (WO-E210). That single rule explains the whole layout — Chapter and ChapterLink are classes, so the feature modules just name them; the shared query would have been a free fn, so it is a static fn on Chapters instead. (pub cannot prefix an @table class — recorded gap #1 — but nothing needs it to.)

Decisions that are not obvious from the code

  • Chapters are rows, not constants. seed_if_empty() inserts them only when the table answers empty, so a WAL restart keeps admin edits instead of reseeding over them — the sample's own proof of chapter 6's claim. The seed bodies are BUILT with wo-html's builders at boot; after that the table is the truth and the builders are never consulted again.
  • The seam is enforced by where the query sits. Chapters.links() lives with the MODEL and hands the view a multi ChapterLink — a projection, not a cursor. No component in this sample touches the database, which is what lets ChapterNav be the same component on the homepage and on every chapter page, differing only by current.
  • HomePage and ChapterPage hold a Component, not chapter data. The nav arrives as an already-built child component in a slot, so neither page knows what a chapter is. That is content projection — Angular's <ng-content>, with the slot as an ordinary field.
  • Two widths, named once. AppShell carries a container field and layout/app.wo exports reading_shell / wide_shell. The Tailwind class strings appear in exactly one place instead of being repeated at every call site.
  • Auth is handler-side by doctrine. The framework ships mechanism (bearer_token, constant-time ct_eq); which routes are gated and by which token is policy, so AdminEdit checks its own field. No global middleware — the public pages stay public.
  • ok_html is the framework's, beside ok_text/ok_json: a status line plus a content-type is transport, not rendering.
  • \$ in chapter code samples. Chapter sources show interpolation (${port}) inside string literals of a language that interpolates — the lexer's \$ escape keeps them literal; code_block() then HTML-escapes the result. This is also why those two samples stay escaped "..." strings rather than becoming raw literals: a raw literal has no escape character, so it cannot spell a literal ${.
  • Concat spans lines two ways now. A line ENDING in .. continues on the next (the one newline suppression in the language) — it never works at the START of a line. For markup, prefer the backtick raw literal: real newlines, real double-quoted attributes, source indentation removed at compile time, ${ } raw and {{ }} auto-escaping. The old ".. does not straddle newlines, so build accumulator-style" note is obsolete and was removed.
  • wo-html's sheet is static. Tailwind's class NAMES, one hand-written CSS string inlined per page by page() — self-contained responses, no toolchain; growing the sheet is appending a line in tw_css().

Gate: just site — see scripts/site-accept.sh (11 checks; the restart leg polls /health instead of sleeping, so it does not share web-app-accept's 0.5s boot race).