Maurice
3b05a59b19
"Add, reorder and rename days" still described the reorder popup as it was before #2485: Move up, Move down and one Add day at the end, and its picture showed that popup. The guide has five steps now. The reorder step names the bin on each day and the two ways of adding one, the next date or Without date, and a new step shows the question before a day goes, with what goes with it, answered with Cancel. The first step says that shortening the dates lists the days that go, and the tip says moving days can be undone and deleting one cannot. All 23 languages use the labels their own interface shows. The picture script looked for the Add day button that #2485 removed, so it could not run any more. It frames the popup itself now, asks about the second day so the question has places and a booking to list, and clicks the first day a second time when the steps before left it selected and the first click folded its panel away.
@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.