Sebastian Fischer
ec78cfbdd0
A multi-day hike restocks on the way: bread in the morning, food for lunch and supper every day or two. Neither could be searched for. - Explore pill: new `bakery` and `supermarket` chips. `supermarket` already existed on the server (shop=supermarket|convenience) but no pill offered it; `bakery` is new (shop=bakery). - Along the tour: `bakery` and `supermarket` are offered to a hike, after its existing kinds so a new hike still starts on the same three. - TREK places index: `bakery` maps to food_and_drink>casual_eatery>bakery; `supermarket` is narrowed to grocery and convenience stores, since the whole food_and_beverage_store branch also brought tobacconists and wine shops. Both paths checked against a live answer of the index. As the more specific term, a bakery is no longer listed as a place to eat when only `food` is asked along a tour. - Category guess: a bakery or grocer picked from the map was preselected as Bar/Cafe or Shopping even where the admin had made a Bakery or Groceries category. The guess now looks for such a category first, by name in the usual languages or by icon, and keeps the broad one when there is none. The category icon picker offers Croissant and ShoppingBasket, the icons the map chips use. - Labels in every locale; MCP tool description names the new kinds.
@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.