ores.ts
Table of Contents
This page is the node for the ores.ts technical space in the codegen
physical-space address graph. Its title is its MASD address; it gathers the
facets generated for this technical space. Each facet is its own document,
linked from the table below. Codegen traverses this graph (root → technical
space → facet → archetype) to resolve which archetypes an entity generates.
1. Summary
The TypeScript projection gives the client the same message shapes the C++ services speak, without hand-copying them. Every facet here renders from the org models that already drive the C++ facets, so the two projections cannot drift.
2. Shared conventions
{{{ts_license}}}triple-stache injects the licence header and the generated-file marker.- Field names stay
snake_case. They are the JSON keys rfl::json writes from the C++ member names, so the TypeScript field name and the key on the wire are one string. - Type names take PascalCase (
login_request→LoginRequest), because a type name is internal to TypeScript and never crosses the wire.
3. Facets
Facets in this technical space — each links to its own node doc. Generated; do not edit by hand.
| Facet | Archetypes | Description |
|---|---|---|
| ores.ts.domain | 1 | Per-entity and per-junction domain interfaces: the TypeScript shape of the object the C++ domain class declares. |
| ores.ts.protocol | 1 | Wire payload interfaces and NATS subject constants. |
4. See also
- Parent: the
oresphysical-space root. - ores.cpp — the C++ projection of the same models.