Send linkedSignalId when creating a reply draft - #81
Merged
Conversation
The composer now tells the backend which specific inbound message a draft is replying to, so DraftSendWorker can resolve the correct In-Reply-To/References Message-ID at send time instead of guessing from the thread.
Preview deployedURL: https://email.rhosys.cloud/pr/claude-linked-signal-id-reply-ui/ |
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
2 participants
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.
Summary
startDraft()inThreadDetailView.vuenow passeslinkedSignalId(the signal being replied to) when creating a draftlinkedSignalId?: stringtoCreateDraftSignalBodyinsrc/types/server.tsContext
Companion change to rhosys/ses-email-adapter#80, which added a
linkedSignalIdfield on outbound signal creation soDraftSendWorkercan resolve the correctIn-Reply-To/ReferencesMessage-ID at send time instead of inferring it from the thread. This PR wires the UI's reply flow to actually populate that field: when the user opens the reply composer from a thread, the signal being replied to (replyTo) is now sent aslinkedSignalIdon draft creation.Test plan
npx vitest run— full suite (67 files, 510 tests) passes, including an updated assertion intests/component/ThreadDetailView.test.tsverifyinglinkedSignalIdis sentnpx vue-tsc --noEmit— cleannpx eslint . --ext .ts,.vue— cleanGenerated by Claude Code