Maurice
3c78452c14
With a room kept for the whole trip and a second stay for a night away, the day after the side trip took the first stay in the list as the hotel it woke up in. The Days view then drew a drive from the kept room, often hundreds of kilometres away, to the side trip's first stop or airport, next to the flight back. The morning now belongs to the stay checked into last, and the evening to the stay that runs on past the day. The map also passes a booking's own point at the edge of the day, as the sidebar already did, so a taxi leaving from the hotel adds no zero-length road from the hotel to itself. The Tour booking type read like the Tours tab, and a booked food tour left people looking at an empty Tours tab. It is now called Guided tour in every language, the empty Tours tab says that booked tours go under Bookings, and the help center and wiki use the new name. The stored type stays 'tour'.
@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.