Maurice
2ffe4d6054
With connected days the drive from one day's last stop to the next day's first is drawn at the head of the arriving card, in the colour of the day before. anchorFor only knew that stretch as a night spill, so a click on it anchored to the arriving card's first stop: the via was stored on the leg after that stop, and the next day drove out to the point, turned and came back, while the stretch that was clicked kept its shape. assembleRoadtrip now names the stop that joined drive leaves from, and anchorFor treats it like the stop a night drive left from. Placing and dragging both resolve to the previous day's last stop, which is the anchor the seam request already reads its vias from.
@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.