Maurice
091ebed8e4
routing_valhalla_provider (fossgis, trek or custom) sits beside the routing URLs under Admin, Default user settings, admin only and locked on a managed install. Without a choice an own Valhalla is custom, an own OSRM alone asks no Valhalla, and otherwise the TREK services answer. The planner asks them through the same-origin relay, so no connect-src changes. A relay that answers 401 (a shared page without a sign-in), 403, 413, 429 or 5xx sends the question to FOSSGIS without a word and is left alone for ten minutes. A long line to describe goes as a polyline.
@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.