Repository navigation
Support HTML files and full readback for Gmail drafts - #39
Merged
Merged
Conversation
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.
Gmail draft create and update now accept a UTF-8 --html-file alongside the existing plain --file or --text, preserving multipart alternatives and attachments through the existing API. Draft JSON includes HTML, and draft get --html prints it for readback. Preview stays read-only and rejects two stdin consumers. Validation: 39 targeted Gmail/Drive CLI and API tests passed, including synthetic provider MIME and HTML readback; full suite runs in CI.