The [routes|...|] quasi-quoter. Captures use RFC 6570 URI-template syntax — {name} for a single segment, {+name} for a splat — and ?name1&name2 for query-string parameters.

[routes|PostsController
GET    /posts                 PostsAction
GET    /posts/{postId}        ShowPostAction
PATCH  /posts/{postId}        UpdatePostAction
GET    /search?q&page         SearchAction
|]

Query parameters are declared explicitly: each ?name names a record field on the action constructor that the URL carries in the query string. The field's Haskell type determines the shape: plain a is required (missing/unparseable ⇒ 404), Maybe a is optional, [a] collects repeated values (?tags=a&tags=b). Every record field of the action constructor must be covered by either a path capture or a query-param entry — unbound fields fail at splice time with a pointer to the exact fields left over.

Renaming. To map a capture or query-param name to a differently named record field, use the { field = #name } syntax after the action. Works for path captures and query params alike:

GET /ShowPost?id     ShowPostAction { postId = #id }
GET /users/{uid}     ShowUserAction { userId = #uid }

This is the ihp-router (plain-WAI) flavour of the quoter — emits HasPath instances and a per-controller <ctrlLower>Trie binding only. IHP apps use the wrapping quoter from IHP.Router.IHP (re-exported through IHP.Router.DSL), which additionally emits the IHP-flavoured CanRoute instance and lowercase-header webRoutes binding.

Three header forms — all top-level declarations:

1. Single-controller. Uppercase-initial header = controller type.
2. Binding-named (multi-controller). Lowercase-initial header is the name of a binding the splice emits. In ihp-router it carries the per-controller trie values; in IHP it additionally carries the [ControllerRoute app] list for FrontController.controllers.
3. No header. Multi-controller, instances + trie values only.

The default splice for the [routes|…|] quoter in ihp-router. Emits the IHP-free declarations a plain WAI app needs — an instance HasPath Ctrl per controller and a parameterised <ctrlLower>Trie :: (Ctrl -> Application) -> RouteTrie binding per controller.

IHP apps don't call this directly; they use the IHP-flavoured routes quoter from IHP.Router.IHP, which composes genericEmit with its own IHP-specific CanRoute / webRoutes emission.

The IHP-free entry point: parses the DSL, reifies the controller(s), and emits genericEmit's output. Suitable for plain WAI applications.

Same as routesDec; provided under the more descriptive name so the IHP-side shim can call it explicitly when composing the IHP-flavoured quoter.

Parse the DSL body, reify each referenced controller type, and validate every route against its action constructor. Returns a ParsedBlock both emitters can consume.

WebSocket routes (those whose routeKind is WebSocketRoute) are split out into pbWsRoutes rather than going through groupRoutesByParent / validateRoute — they reference a WSApp type by name (not an action constructor of a controller), so the HTTP-route validation pipeline doesn't apply. For v1 we also restrict WS routes to the lowercase-header form, since the IHP shim only knows how to register them through the webRoutes binding the lowercase form emits.

Emit the generic HasPath instance per controller plus the top-level <ctrlLower>Trie binding per controller. No IHP-specific references — this is the half that moves to ihp-router in the extraction PR.

A parsed [routes|…|] body, ready for emission. Produced by parseAndReify and consumed by genericEmit and ihpEmit.

Which of the three header forms the parser saw.

Top-level binding name for the per-controller trie value: e.g. PostsController becomes postsControllerTrie. Both the emitter (emitTrieValue) and any IHP-side wrapper that wants to call the binding with a specific dispatch function (e.g. IHP.Router.IHP.emitCanRoute) use this helper to agree on the name.