trails

trails-cool/trails

Fork 0

Commit graph

Author	SHA1	Message	Date
Ullrich Schäfer	079c3de90c	Modernise zod idioms to v4 Replace the deprecated v3 string-method forms with the top-level validator helpers zod 4 prefers: - z.string().url() → z.url() (3 sites) - z.string().uuid() → z.uuid() (5 sites) - z.string().datetime() → z.iso.datetime() (9 sites) Also swap the ZodIssueCode.custom compat-shim reference in demo-bot.server.ts's superRefine for the bare string literal "custom", which is v4's idiomatic form. No runtime change. All 147 tests still pass. The `parsed.error.issues.map(i => ({field, message}))` pattern in the five journal API route handlers stays as-is — the fields we read are unchanged in v4, and zod's new error helpers (z.treeifyError, z.prettifyError) produce different shapes that would change our public API error contract. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-19 11:41:03 +02:00
Ullrich Schäfer	49b304749e	Add @trails-cool/api package with Zod schemas for REST API contract Single source of truth for the Journal REST API: - API_VERSION semver constant (1.0.0) - Endpoint path constants (routes, activities, auth, uploads, push) - Zod schemas for all request/response shapes: - Routes: list, detail, create, update, compute - Activities: list, detail, create - Auth: token exchange, refresh, device management - Discovery: instance info + API version - Uploads: presigned URL flow - Errors: structured error response with field-level details - Cursor-based pagination schemas - TypeScript types inferred from Zod (z.infer) Used by Journal server (validation) and mobile client (type safety). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-12 22:49:30 +02:00

Author

SHA1

Message

Date

Ullrich Schäfer

079c3de90c

Modernise zod idioms to v4

Replace the deprecated v3 string-method forms with the top-level
validator helpers zod 4 prefers:

- z.string().url()      → z.url()      (3 sites)
- z.string().uuid()     → z.uuid()     (5 sites)
- z.string().datetime() → z.iso.datetime() (9 sites)

Also swap the ZodIssueCode.custom compat-shim reference in
demo-bot.server.ts's superRefine for the bare string literal "custom",
which is v4's idiomatic form. No runtime change.

All 147 tests still pass.

The `parsed.error.issues.map(i => ({field, message}))` pattern in the
five journal API route handlers stays as-is — the fields we read are
unchanged in v4, and zod's new error helpers (z.treeifyError,
z.prettifyError) produce different shapes that would change our
public API error contract.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-19 11:41:03 +02:00

Ullrich Schäfer

49b304749e

Add @trails-cool/api package with Zod schemas for REST API contract

Single source of truth for the Journal REST API:
- API_VERSION semver constant (1.0.0)
- Endpoint path constants (routes, activities, auth, uploads, push)
- Zod schemas for all request/response shapes:
  - Routes: list, detail, create, update, compute
  - Activities: list, detail, create
  - Auth: token exchange, refresh, device management
  - Discovery: instance info + API version
  - Uploads: presigned URL flow
  - Errors: structured error response with field-level details
- Cursor-based pagination schemas
- TypeScript types inferred from Zod (z.infer)

Used by Journal server (validation) and mobile client (type safety).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-12 22:49:30 +02:00

2 commits