microsoftgraph / microsoftgraph/msgraph-metadata
`msgraph-sdk-python` expects a response from `/drives/{drive-id}/items/{driveItem-id}/copy`
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
This issue is created as a follow-up to this pull request.
In msgraph-sdk-python the CopyRequestBuilder (that uses /drives/{drive-id}/items/{driveItem-id}/copy API endpoint) on POST is expecting a DriveItem as a response from Microsoft Graph, while the driveitem_copy REST API doesn't return anything.
The code change that I suggested in the pull request mentioned above fixes the problem. But it affects the auto-generated code, so I was asked to create this issue.
More info can also be found in this issue on msgraph-sdk-python.
Contributor guide
No contributing guide indexed for this repository
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
Start with the driveItem copy REST API response documentation and the CopyRequestBuilder behavior described here, then inspect the proposed change in pull request #830. The metadata should generate a POST operation for this endpoint without expecting a DriveItem response; verify the resulting SDK behavior against the related issue #334.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100