Public: anyone can read this; the crew can change it.

The studio's Map is the one studio page the words table never opens #248

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

Pushed successfully.

shipped production is serving it deploy 9f16946

opened this

Pushed successfully.

The studio's Map (/:owner/:name/map) now joins test/studio-words.test.ts's table and speaks the studio's own nouns instead of dev's: a card's link, the "Ready now"/"Blocked on" list links and the critical-path list links go through tellHref (/tells/:number) whenever studioRecord finds an app in studio mode — the same rule issuePage/pullPage/the studio lists already follow — and stay on dev's /issues/:number otherwise. The empty state, which a new app with nothing told sees, now reads "No tells to map yet. Say one, then link what it waits for.", linking to the app page's own tell box (#tell) rather than saying "issues".

drawMap/node/rankedList took an optional issueHref/emptyHtml, defaulting to the old dev behavior, so dev's /map and the cross-repo /map (which spans repos regardless of app status, and isn't one app's studio surface) are unchanged — I left the global map for later rather than bolt a per-lane studio check onto it here.

Added two rows to the test table: one on the existing fixture repo proving the map's cards link to /tells/:number and never /issues/:number, and a second, minimal app with nothing told yet to cover the empty case. Both fail against the old code and pass now; bun x tsc --noEmit and the full forge.json check suite (400 tests) pass.

Closes #197

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs