Wrongly defined `delta` on messages
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start with the generated users/item/messages/messages_request_builder.py definition around line 140 and compare it with the Microsoft Graph message resource documentation. Check how the messages delta request is exposed and confirm the unsupported API behavior; done means the invalid messages-level delta operation is no longer defined or is otherwise aligned with the documented per-mailfolder support.
Written by the indexing model from the issue text.
Description
Describe the bug
We define a delta on messages (https://github.com/microsoftgraph/msgraph-sdk-python/blob/9542fa0b95c58822968116896048a00fe911eda4/msgraph/generated/users/item/messages/messages_request_builder.py#L140) that can be used like await client.users.by_user_id(some_id).messages.delta.get(), however the API doesn't support this (yet) and thus simply returns Unsupported request: Change tracking is not supported against 'microsoft.graph.message'.
Tracking changes on messages, according to the docs, only exists on a per mailfolder basis. message resource type
Expected behavior
Not having it defined (or get Graph API to finally support tracking).
How to reproduce
Given some GraphServiceClient client, a user or mailbox with id some_id and appropriate permissions call:
await client.users.by_user_id(some_id).messages.delta.get()
SDK Version
No response
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
No response
Configuration
No response
Other information
Disclaimer this might as well not be a msgraph-sdk-python issue but generally wrongly defined in the msgraph-sdk. I'm reporting it here because I only checked here.
- Dominant language
- Python
- Stars
- 630
- Forks
- 96
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
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.
More from microsoftgraph/msgraph-sdk-python
-
status:waiting-for-triage type:bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
microsoftgraph/msgraph-sdk-python#1570 ·
-
status:waiting-for-triage type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoftgraph/msgraph-sdk-python#1563 ·
-
Needs: Attention :wave: type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoftgraph/msgraph-sdk-python#1287 · 2 comments · 1 reaction ·
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
microsoftgraph/msgraph-sdk-python#1578 ·
-
status:waiting-for-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoftgraph/msgraph-sdk-python#1557 ·
All issues in microsoftgraph/msgraph-sdk-python
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
StevenBlack/hosts#3256 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
qualcomm/qai-appbuilder#275 ·