Maurice
bafb74f872
Putting a multi-day tour on a day through any of the usual ways put the whole tour on that one day. Now the way it goes on is a choice: the whole tour on this day, or stage 1 on this day and each next stage on the next day of the trip. The day menu of the tour lists and the detail's "Add to day" ask in the same menu, as a second step after the day; a tour dragged onto a day, or added from a place where no menu asked, gets a small dialog on the desktop and a card on the phone. Only the trip's days are used: when fewer days are left than stages, the menu says up to which stage fits and the rest stay without a day. A stage already on a day moves to its new day, the whole tour comes off the days it was on, and a stage the route no longer has comes off too. The writes run in order through the store, the repo and the mutation queue, so they work offline, and one undo takes the spread back, the whole tour onto its day again. The plan lives in stageSpread.ts, the writes and the question in useTourDayChoice, which every way onto a day now passes through on both the desktop and the phone.
@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.