fix: properly track isProcessing state to block duplicate message submission

The isProcessing field existed on conversations but was never set to true
in production code, making all submission guards effectively no-ops.

- Add setProcessingForConversation to conversations store and claude.ts
- Set isProcessing=true after send_prompt succeeds in handleSubmit and handleQuickAction
- Set isProcessing=false when claude:state emits idle, success, or error
- Add tests for the new setProcessingForConversation logic
This commit is contained in:
2026-03-09 14:20:33 -07:00
committed by Naomi Carrigan
parent 9ad88fda2d
commit 0f3ad0dbee
5 changed files with 116 additions and 0 deletions
+1
View File
@@ -41,6 +41,7 @@ export const claudeStore = {
setWorkingDirectory: conversationsStore.setWorkingDirectory,
setWorkingDirectoryForConversation: conversationsStore.setWorkingDirectoryForConversation,
setProcessing: conversationsStore.setProcessing,
setProcessingForConversation: conversationsStore.setProcessingForConversation,
addLine: conversationsStore.addLine,
addLineToConversation: conversationsStore.addLineToConversation,
updateLine: conversationsStore.updateLine,