[NikolaGoranNaumovski]

🎯 Goal

Let users manage their pending scheduled messages from the scheduled message list: edit, reschedule, send now, delete, and copy the text of a message whose channel was deleted. This follows the web designs for the row menu, the edit preview and the delete confirmation (Figma: Scheduled List and Edit, Reschedule and Delete sections).

Part of the scheduled messages feature (REACT-1389). Stacked on #3366 (list) and depends on GetStream/stream-chat-js#1915 (state layer) and GetStream/stream-chat-js#1956 (composer edit mode).

🛠 Implementation details

Row menu (ScheduledMessageActions)

• Each list item gets an actions button that opens a ContextMenu. Which actions appear depends on the status:
  • scheduled: Edit, Reschedule, Send now, Delete
  • failed: Delete
  • failed because the channel was deleted (channel_deleted): Copy, Delete
  • sending: the button is disabled
• Edit appears only when the host passes an onEdit handler. Both hosts do: the banner's list dialog and the Channel Detail section.
• Action rules live in a pure util, getScheduledMessageActions.

Actions

• Reschedule: opens RescheduleMessageDialog, pre-filled with the current time, and saves through client.scheduledMessages.updateScheduledMessage(id, { scheduled_at }).
• Send now: calls sendScheduledMessageNow and confirms with a "Message sent" toast. The item leaves the list on scheduled_message.sent.
• Delete: asks for confirmation (DeleteScheduledMessageAlert), then calls deleteScheduledMessage.
• Copy: copies the message text to the clipboard.
• Failures: reported as typed notifications. The new translateScheduledMessageActionFailed translates them by reason:
  • a 404 shows "Already sent", and the store has already dropped the item;
  • sending, conflict, not-editable and too-soon / too-far each get their own copy;
  • anything else falls back to a generic message for that action.
• Conflicts: a 409 conflict reloads the store.

Shared date/time dialog

• The form inside ScheduleMessageDialog is extracted into ScheduleTimeDialog. It takes the channel, preview, title, error text and submit function as props, so scheduling and rescheduling use the same dialog.
• useScheduleTimeForm now takes { channel, initialScheduledAt? }.
• The new useScheduleTimeSubmit runs any submit function, and useScheduleMessageSubmit wraps it.
• ScheduleMessageDialog renders the same as before.

Edit mode in the composer

• Edit calls composer.editScheduledMessage(scheduledMessage):
  • from the banner's list, on that banner's composer (channel or thread);
  • from Channel Detail, on the channel's composer, after closing the modal.
• While editing:
  • the composer shows EditedScheduledMessagePreview, with cancel calling cancelEditScheduledMessage();
  • useSubmitHandler sends Enter and Send to updateScheduledMessage() instead of sendMessage / editMessage;
  • the send button shows the checkmark;
  • useCanScheduleMessage hides the schedule button.
• New ComponentContext slot: EditedScheduledMessagePreview.
• If the message is sent, deleted or fails elsewhere during the edit, MessageComposer ends the edit (feat: schedule and edit scheduled messages from MessageComposer stream-chat-js#1956). The new translateScheduledMessageCompositionEnded explains why: "This scheduled message was already sent / was deleted / failed to send".

Not in this PR

• Editing a failed message, which means scheduling it again with a fresh message.id. The server rejects a PATCH on failed messages with 120, so this needs a new composer method and moves to REACT-1390 (feat(ScheduledMessages): handle failed scheduled messages (REACT-1390) #3372, using MessageComposer.rescheduleFailedMessage from feat: schedule and edit scheduled messages from MessageComposer stream-chat-js#1956). Failed items offer Delete (and Copy for deleted channels) for now.
• Text in the UI follows the Figma structure, but the exact copy couldn't be read from Figma yet. It will be aligned once it can.

Translations
21 new strings in all 12 locales.

Commits

1. refactor: share the date and time dialog
2. feat: row menu with reschedule, send now, delete and copy
3. feat: edit scheduled messages in the composer
4. feat(i18n): translations
5. feat: explain why a scheduled message edit ended
6. feat(i18n): translations for it

Commits 1–3 each typecheck and pass the scheduled-message, composer, Channel Detail and i18n tests on their own. The full suite passes on the last commit (3460 tests).

Testing

• Unit:
  • action rules per status;
  • each action (send now, delete confirm / cancel, reschedule pre-fill and submit, reschedule failure keeps the dialog open, copy);
  • the edit flow (preview, schedule button hidden, Enter / Send save via updateScheduledMessage with no sendMessage, cancel restores the earlier draft);
  • the translator per reason and per action;
  • axe on the open menu.
• Manual in examples/vite against the scheduled messages test app:
  • reschedule moved the item to the new time;
  • Edit → Enter saved the text through PATCH, and nothing appeared in the channel;
  • Delete with confirmation emptied the list;
  • no console errors.

🎨 UI Changes

Screenshots: row menu (scheduled), row menu (deleted channel), reschedule dialog, delete confirmation, edit preview in the composer.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.