Repository navigation
feat(chat): keep what the owner was writing when they switch chats - #127
Merged
Merged
Conversation
The composer text lived in component state, so going to another chat and back lost it. Each bot now has its own draft, kept in memory while the app is open (never on disk, since a message can carry personal data). The composer is keyed by bot so drafts and pending notes do not leak between chats. Files picked but not sent are still not kept. Spec 15.1 updated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
If you typed something in a chat, went to another chat and came back, the text was gone.
What
app/src/features/chat/drafts.ts). The composer starts from that draft and updates it as you type. Sending clears it.Checks
pnpm checkpasses (287 tests).