Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: fix CopyRequestBuilder.post() to not expect a response #830

Closed
wants to merge 1 commit into from

Conversation

aberezh
Copy link

@aberezh aberezh commented Jul 28, 2024

CopyRequestBuilder.post() method was expecting a DriveItem as a response, while the driveitem_copy REST API doesn't return anything - https://learn.microsoft.com/en-us/onedrive/developer/rest-api/api/driveitem_copy#response

#334

The method was expecting a `DriveItem` as a response, while the `driveitem_copy` REST API doesn't return anything - https://learn.microsoft.com/en-us/onedrive/developer/rest-api/api/driveitem_copy#response

microsoftgraph#334
@aberezh aberezh requested a review from a team as a code owner July 28, 2024 15:20
Copy link
Member

@baywet baywet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @aberezh,
Thank you for your contribution.
Unfortunately, we cannot accept it because it targets parts of a code that are auto generated.
This means that next weekly generation it would get overwritten.
But this gets generated from the service metadata we process and if we fix the metadata information we would be able to generate the right method prototype.
Can you open a new issue in this repository so we can start looking into fixing the metadata please?
https://GitHub.com/Microsoftgraph/msgraph-metadata

@aberezh
Copy link
Author

aberezh commented Jul 30, 2024

@baywet Thank you for your reply. I was afraid the code might be auto-generated. But since it's a one-line change, I decided it's easier to just create a PR.
Here is the issue I created on msgraph-metadata as you asked.

Closing the PR in this case.

@aberezh aberezh closed this Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants