Maurice
bbcf17d816
The stays Dawarich recorded used to be a panel above the timeline: every open stay of every day, stacked over the entries. A fortnight of driving puts forty of them between the reader and their own first entry, which is the scrolling Roel described on the 16th. They belong where the day is. Each day of the timeline now ends in one line: the Dawarich mark, how many stays, and the span they cover. A tap opens them, and what opens is the panel's own rows, imported rather than copied — one row this detailed in two places would be two things to keep in step and a straight hit on the duplication budget. Nothing is drawn on a day with nothing pending. A stay falls on the day it happened, which is often a day the journal has no entry on yet, and that is the whole point of offering it. Those days join the timeline so their stays can be reached at all; without that the only way to a quiet day's stays would be to write an entry on it first. Not while a search is running, where a day whose entries the query filtered out is not a day the reader is looking at. The count takes two keys picked by the number, the shape this codebase already uses for a noun that changes with it: there is no plural engine in the i18n layer, and one key with a placeholder in it reads as "1 stays". Russian, Polish, Czech, Ukrainian and Arabic inflect again at 2-4 and 5+, which two forms cannot express, so their plural puts the number after a colon, where no form has to agree with it. The phone is untouched: it opens the same list in a sheet from its own button, which is where it works on a screen that shows one entry at a time.
@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.