stacklok / toolhive-studio / 24716472404

70%

push

github

feat(playground): persist composer drafts per thread across route changes (#2048)

* feat(playground): add useThreadDraft hook for per-thread composer drafts

Adds a small hook that persists the Playground composer text to localStorage under toolhive.playground.draft.<threadId>, plus a clearThreadDraft helper for external cleanup.

The hook expects the consuming component to be keyed by threadId, so a thread switch remounts and the lazy useState initializer re-reads the stored draft — no useEffect needed. Writes go through a useCallback that removes the key when the draft is cleared to empty.

Tests cover empty-state, existing-draft load, persist-on-update, clear-on-empty, undefined-threadId fallback, remount-with-different-threadId, and clearThreadDraft behavior.

* feat(playground): persist composer drafts across route and thread changes

The Playground composer text lived only in component state, so navigating away from /playground/chat/$threadId (or switching thread) discarded any unsent draft. This wires ChatInputPrompt to the useThreadDraft hook so drafts survive both.

- Add a threadId prop to ChatInputPrompt and replace useState('') with useThreadDraft(threadId)

- Key both ChatInputPrompt instances by threadId in ChatInterface so a thread switch remounts the composer — the lazy initializer re-reads the right draft, and as a bonus the internal PromptInput attachments reset too (previously they bled across threads)

- Call clearThreadDraft inside handleDeleteThread so removing a thread doesn't leave an orphan localStorage key

* refactor: adjust types

* fix(playground): keep draft and current thread when delete fails

deleteThread previously returned null both when the IPC call failed and when the last thread was successfully deleted, so callers could not distinguish the two. The route's delete handler treated any null as success and unconditionally wiped the stored draft via clearThreadDraft, even when the thread still existed.

- Change dele... (continued)

3743 of 6183 branches covered (60.54%)

40 of 43 new or added lines in 4 files covered. (93.02%)

5860 of 8891 relevant lines covered (65.91%)

119.38 hits per line