trails/apps/planner
Ullrich Schäfer 14b179bb0c Fix waypoint loading in Edit in Planner flow
Three issues fixed:

1. GPX parser used browser DOMParser which doesn't exist in Node/Vite SSR.
   Added async parseGpxAsync() using linkedom for server-side parsing.

2. Server-side session initialization stored waypoints in a Yjs doc
   instance separate from the Vite WebSocket plugin's doc store.
   Moved waypoint initialization to client-side: API returns parsed
   waypoints, client adds them to Yjs after sync.

3. GPX was encoded in URL params causing HTTP 431. Now the Journal
   creates a Planner session via API (POST body), and only passes
   compact waypoint coordinates in URL params.

Verified: Journal route → Edit in Planner → 4 waypoints loaded,
route computed (79.3km), elevation profile, Save to Journal ready.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-24 20:22:58 +00:00
..
app Fix waypoint loading in Edit in Planner flow 2026-03-24 20:22:58 +00:00
Dockerfile Add infrastructure: Terraform, Docker Compose, BRouter, CD pipeline (#2) 2026-03-22 13:32:01 +01:00
package.json Fix Yjs WebSocket in dev mode 2026-03-23 01:12:13 +01:00
react-router.config.ts Complete monorepo toolchain setup (tasks 1.1-1.7) 2026-03-22 12:12:57 +01:00
server.ts Add Planner session management with Yjs WebSocket (#1) 2026-03-22 13:26:03 +01:00
tsconfig.json Add Planner session management with Yjs WebSocket (#1) 2026-03-22 13:26:03 +01:00
vite.config.ts Fix Yjs WebSocket in dev mode 2026-03-23 01:12:13 +01:00