Archived
fix: scope the attachment sending indicator per session
isSendingPrompt was a single global flag, so an in-flight upload showed the "Sending…" dock on whatever session/machine the user switched to. Replace it with sendingPrompts, a Record<sessionId, true> keyed like sessionStatuses/sessionActivities. The controller sets/clears the entry for the originating session (captured before the await), the chat dock reads only the selected session's entry, and the session list now shows the activity dot for a session that is uploading so progress is visible after switching away. Machine switches clear the record like other per-session state; deselecting a session no longer cancels its indicator.
This commit is contained in:
@@ -2,4 +2,4 @@
|
||||
"@jmfederico/pi-web": patch
|
||||
---
|
||||
|
||||
Show a sending indicator in the chat while messages with image attachments are uploading. Previously the composer cleared instantly while the upload, server-side image resizing, and first-session open happened in the background, so it looked like nothing was happening. The existing chat activity dock now shows "Sending your message…" during that window (including the folder-mode upload step) and is superseded by the real session activity once the message lands. Attachment sending is now orchestrated in the session controller so there is a single, consistent indicator.
|
||||
Show a per-session sending indicator while messages with image attachments are uploading. Previously the composer cleared instantly while the upload, server-side image resizing, and first-session open happened in the background, so it looked like nothing was happening. The chat activity dock now shows "Sending your message…" for the originating session (including the folder-mode upload step), and that session shows the activity dot in the session list so progress is visible even after switching away. The indicator is scoped per session, so it no longer leaks onto other sessions or machines, and the upload itself continues in the background regardless of navigation.
|
||||
|
||||
Reference in New Issue
Block a user