Skip to content

Input message queued#74

Merged
kentcdodds merged 1 commit into
mainfrom
cursor/input-message-queued-5ff8
Feb 2, 2026
Merged

Input message queued#74
kentcdodds merged 1 commit into
mainfrom
cursor/input-message-queued-5ff8

Conversation

@kentcdodds
Copy link
Copy Markdown
Member

@kentcdodds kentcdodds commented Feb 2, 2026

Clears the message input field after a message has been successfully queued, improving user experience by indicating successful submission and preparing for the next message.

Test Plan

  1. Run npm run dev.
  2. Navigate to a recipient's chat page.
  3. Type a message into the input field.
  4. Send the message.
  5. Verify that the input field clears after the message is successfully sent (queued).
  6. (Optional) Verify that the input does not clear if there's an error during message sending.

Checklist

  • Tests updated
  • Docs updated

Screenshots


quick-add-input-cleared


Open in Cursor Open in Web


Note

Low Risk
Small, client-side UX change limited to clearing a textarea after successful form submission; no business logic or data handling is modified.

Overview
After successfully submitting a new message on the recipient page, the message textarea now auto-clears once the useFetcher request completes, giving immediate feedback that the message was queued.

The input is preserved when the submission returns validation/server errors, avoiding accidental data loss on failed sends.

Written by Cursor Bugbot for commit e77ffb4. This will update automatically on new commits. Configure here.

Co-authored-by: me <me@kentcdodds.com>
@cursor
Copy link
Copy Markdown

cursor Bot commented Feb 2, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@kentcdodds kentcdodds marked this pull request as ready for review February 2, 2026 20:06
@kentcdodds kentcdodds merged commit e821fec into main Feb 2, 2026
0 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants