Maurice
92af437ff6
The night went to the last visit of the hotel. On a day without hours the booking seats its own stop first, and Days does not show that stop, so a rest the traveller put mid-day was the last visit: it was held to the check-in and the places behind it followed from there, the way the report describes. The night is now the visit that ends the day, else the booking's stop, else the last visit. A visit the traveller adds to the check-in day no longer moves the night or its check-in. nightVisits in shared holds the rule, and the road trip, calculate_roadtrip, the stored ride slot and the stop editor all read it. Refs #2636
@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.