Maurice
d4677bdeab
Every day was scheduled from nothing, so a booking that runs into the next day ended at midnight as far as the chain was concerned. Check in at 08:00 and out at 08:00 the next day, and the rail was happy to put you somewhere else at 07:00 that morning, with no sign that the room was still yours. The day a check-out falls in now starts at the check-out rather than at nothing. A floor, never a move: a stop with a clock of its own keeps it and collects the late finding any leg it cannot make in time would give it, so a plan that says 07:00 still says 07:00 and merely admits it does not add up. A stop with no clock starts at the check-out instead of having no time at all. Only that one day. A stay running Monday to Thursday leaves Tuesday and Wednesday alone, because you sleep there, you do not sit there. The departure chip takes the door-out mark instead of a clock face. Beside an arrival time, a second clock read as a second arrival.
@trek/shared
Single source of truth for TREK's API contracts, expressed as Zod schemas and consumed by both the server (request validation + inferred DTO types) and the client (typed requests/responses).
This package is part of the incremental NestJS + React 19 migration (see the "Brownfield Rewrite" board). It is intentionally dormant until modules start importing it — adding it changes nothing for users.
Rules
- One folder per domain:
src/<domain>/<domain>.schema.ts(+.spec.ts). - Domain-agnostic building blocks live in
src/common/. - A route is only considered migrated once its contract lives here.
- Schemas are the source of truth; server DTOs and client types are inferred from them
(
z.infer<typeof schema>), never hand-duplicated.
Consumption (dev)
Both apps resolve @trek/shared to this package's TypeScript source:
- Server (
tsx): viapathsinserver/tsconfig.json. - Client (
vite): viaresolve.aliasinclient/vite.config.ts(+pathsfor the type-checker).
Production packaging (Docker / workspace wiring) is introduced in card F2, when the server first depends on this package at runtime. Until then prod builds are untouched.
Not yet here
The canonical error envelope is finalised in card F5 (it must match TREK's current Express error responses byte-for-byte), so it is deliberately not invented in F1.