k1nq/TREK

mirror of https://github.com/mauriceboe/TREK.git synced 2026-06-19 13:21:46 +00:00

Files

T

Maurice 219ba78219 feat(transport): support multi-leg (layover) flights in the booking form

A flight booking can now hold an ordered chain of airports (e.g. FRA -> BER ->
HND) instead of a single departure/arrival pair. The route is entered as a list
of waypoints with a '+ add stop' button; each stop carries its own arrival and
departure time plus the airline/flight number of the segment leaving it, while
the whole booking keeps one price.

Stored without a schema change: the existing reservation_endpoints rows carry the
ordered waypoints (from/stop/to by sequence) and a metadata.legs array holds the
per-leg detail. Top-level metadata (departure_airport/arrival_airport/airline/
flight_number) mirrors the first and last leg, so a single-leg flight persists
exactly as before and legacy readers keep working.

2026-06-11 15:38:48 +02:00

scripts

Migrate TREK 3 to NestJS + React 19 (shared Zod contracts) (#1087 )

2026-05-31 21:10:00 +02:00

src

feat(transport): support multi-leg (layover) flights in the booking form

2026-06-11 15:38:48 +02:00

.prettierrc

chore: fix monorepo build pipeline and migrate shared to built package (#1056 )

2026-05-25 21:44:58 +02:00

eslint.config.mjs

chore: move i18n to shared package (#1066 )

2026-05-26 20:27:29 +02:00

package.json

feat(reservations): native booking-confirmation import via KDE KItinerary (#1102 )

2026-06-04 20:40:57 +02:00

README.md

Phase 0 — NestJS + Zod foundation harness (F1–F8) (#1050 )

2026-05-25 14:29:30 +02:00

tsconfig.json

chore: fix monorepo build pipeline and migrate shared to built package (#1056 )

2026-05-25 21:44:58 +02:00

tsup.config.ts

chore: move i18n to shared package (#1066 )

2026-05-26 20:27:29 +02:00

README.md

@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): via paths in server/tsconfig.json.
Client (vite): via resolve.alias in client/vite.config.ts (+ paths for 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.