Maurice
6e1c9e8e9f
- Orders closed at the cloud: the app shows the plans and that TREK Cloud opens soon, and sells only in a test build (TestFlight, App Review), whose sandbox purchases the cloud still sets up; a store purchase it would refuse is never offered. The plans arrive without prices then, the store's own are shown where it gives them. - A purchase paid but never set up (Ask to Buy approved later, the app closed mid-purchase) is picked up by Restore purchases and goes on to the claim with that purchase, instead of failing; nothing is bought twice. - The buy button names the period with the price (guideline 3.1.2). - The privacy link opens the policy without the site's sales header. - The privacy manifest declares what TREK Cloud keeps: email, name, the store purchase, photos, other user content and saved places, all for the app to work, linked to the account, never for tracking. - The email hint promises messages about the contract, not receipts, which the store sends.
@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.