ReservationsController's 4 grandfathered @Body() params now validate through the global ZodValidationPipe (createZodDto over the existing @trek/shared schemas); their allow-list entries are removed (the boot gate rejects stale entries). The bespoke 400 bodies (Title is required / positions must be an array / user_ids must be an array) become the pipe's field envelope, and non-numeric traveler ids now 400 instead of being silently dropped. reservationPositionsRequestSchema is loosened to the real wire contract: day_plan_position is optional (the legacy route never validated position items and an absent value binds NULL) — pinned by RESV-006. AccommodationsController stays grandfathered until the dayService migration.
@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.