Skip to content

v1.0.202

Choose a tag to compare

View all tags
@github-actions github-actions released this 06 May 18:22
· 98 commits to main since this release
v1.0.202
65d8b11

✨ New: the chip view has a name — Code Map

The chip view shipped in v1.0.198: every function rendered as a card with caller pins on the left, callees on the right, click to walk the call graph. Until now it was awkwardly labelled Block / 代码块 in the toolbar — a holdover from how the components are named internally. This release renames it to Code Map / 代码地图 everywhere a user can see it.

  • File Browser toolbar: the third reading-mode button (Edit / Blame / Code Map) opens the chip view
  • Git Changes diff toggle: File / Map instead of File / Block
  • Empty state, loading, and unsupported-file messages all unified
  • Internal state is now 'code' | 'map' end-to-end, matching the rest of the file browser

No behavior changes — same view, consistent name. Component / hook / file names stay BlockViewer, BlockDiffViewer, BlockDiffMinimap etc., because internally a Code Map is composed of per-function "blocks" / chips. Those names describe the primitive, not the user-facing feature.

🐛 Fix: /try cooldown no longer dumps raw JSON

The "Start Demo" button on cocking.cc/try was a plain <a href> — a full-page navigation. When the function hit its 5-minute cooldown and returned {"error":"Please wait 280s..."}, the browser navigated to that JSON response and rendered it as raw text. Worse, if the user clicked while a slow sandbox-create was already in flight, the working sandbox URL would arrive after the user had left the page and get lost.

The button now fetch-es with Accept: application/json. On success it navigates to the sandbox; on cooldown or error it shows a toast and re-enables the button so you can retry. No-JS fallback via <noscript> still works.

🌐 Site: Code Map on cocking.cc + new blog post

Code Map is now advertised on the homepage and gets its own user-perspective walkthrough in the blog:

  • New homepage section between Bubbles and Modes — chip view + caller/callee pins explained from a usage angle
  • New post "Read code as a map, not a tree" (中文) — five real moments where Code Map saves time: day-one in a new repo, following a call you don't trust, reviewing AI-generated PRs, tracing a bug, reading code with no LSP
  • README updated (EN + ZH): Code Map added to the Explorer features list, the pain table, and the use cases
Assets 2
Loading