Add Microsoft Graph draft, reply, and file attachment flows - #26
Draft
erik-kroon wants to merge 1 commit into
Draft
erik-kroon wants to merge 1 commit into
erik-kroon wants to merge 1 commit into
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.
Applications that compose mail through Microsoft Graph drafts currently hit the unsupported-route fallback when creating a message or reply. This adds the JSON draft lifecycle so clients can create a draft, update it, attach files, send it, and read the saved message and attachment bytes through the existing Graph surface.
createReply, andsend, with delegated scopes and mailbox ownership checks. Sending returns an empty 202 and moves the same message into sent items; replies retain the original conversation and respectreplyTo.hasAttachments.The manifest marks limited operations as partial. This deliberately supports delegated
/meJSON mail with file attachments smaller than 3 MB. MIME, upload sessions, item/reference attachments, generated quoted reply bodies, mail-folder/user-scoped routes and external delivery are outside this change. IDs remain stable even without the immutable-ID preference; default Outlook ID changes are not simulated.Validation:
pnpm install --frozen-lockfilepnpm exec turbo run build --concurrency=3(29 successful tasks)pnpm format:checkandnode scripts/sync-versions.mjs --checkpnpm exec turbo run type-check lint test --concurrency=3(92 successful tasks)pnpm exec turbo run build type-check lint test --filter=@emulators/microsoft --concurrency=2(57 Microsoft tests passed; three existing live tests skipped)No live Microsoft validation was performed. Relevant API contracts: create draft, create reply, add attachment, send draft.