fix: reply drafts honor Reply-To, add Re: and encode non-ASCII subjects - #12
Merged
TheGreatAxios merged 1 commit intoSep 27, 2026
Conversation
TheGreatAxios
added this pull request to stack #9
September 27, 2026 00:46
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.
Closes CL-9439
Reply drafts (
gmail_create_draftwithreplyToMessageId):Reply-Tolist when present, else itsFrom. Replying to a message in SENT still goes to its firstTorecipient.Re:unless it already starts withRe:(any case).to: []counts as absent, so the reply recipients still apply.=?UTF-8?B?…?=, folded into words of at most 75 characters).The newline guards still run on every header value, including the
Reply-Toaddresses. Every tool still asks for approval, and the public API is unchanged.Tests in
src/tools/create-tools.test.tscover Reply-To, SENT,to: [], an existingRE:, and a long mixed-script subject. The Reply-To and encoding tests failed before the fix.