microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
No way to provide base64 encoded MIME content when replying to message.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
Describe the bug
This documentation says there are 2 ways to create a draft reply for an existing outlook message. First way is probably working, but in v5 there is no way to create this Http Post request for sending raw MIME content.
Microsoft.Graph.Me.Messages.Item.CreateReply.CreateReplyPostRequestBody this metadata does not include a property (Content) to provide raw mime.
Expected behavior
There should be a method or metadata update that will enable developers to provide encoded mime content to create reply for a message as a draft.
Additional context
Version 5.4.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Microsoft Graph createReply documentation and the Microsoft.Graph.Me.Messages.Item.CreateReply.CreateReplyPostRequestBody metadata type. Confirm how raw, base64-encoded MIME content is represented by the API and identify the SDK metadata or request path that would need to expose it. Done means a draft reply can be created with raw MIME content and the behavior is covered by an appropriate SDK test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100