Maurice
25282ea1c5
The section stacked a lonely button, a centred line and a small print hint on top of each other, and the create dialog used bare browser checkboxes that ignore the accent. The dialog now runs on the shared Modal with selectable scope tiles, keys render as cards with their scopes as chips, deletion goes through ConfirmDialog, and the endpoint sits in its own row with a copy button. Pressing Enter in the name field with every scope switched off used to create a key: the empty list was dropped from the request and the server stored it as a key that reads everything. Creation is now refused until at least one scope is picked. A failed list load no longer reads as "no keys yet", the create button stops at the server's limit of ten keys, a refused clipboard says so, and SQLite timestamps are parsed so Safari does not show Invalid Date.
@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.