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

Require at least one Object in deleteObjects requests #386

Merged
merged 1 commit into from
Feb 7, 2019
Merged

Conversation

kherock
Copy link
Collaborator

@kherock kherock commented Feb 7, 2019

Due to the way XML works, it's actually impossible to specify an empty array of Objects, so my concerns that an empty array would actually be allowed don't apply.

@kherock kherock merged commit 53eb263 into master Feb 7, 2019
error = err;
}
expect(error).to.exist;
expect(error.code).to.equal("MalformedXML");
Copy link
Collaborator

Choose a reason for hiding this comment

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

@kherock Do you think this could break users' code? I can imagine a naive deleteObject user might make empty requests sometimes. Should this be released in a patch, minor, or major release?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

As of a few patches ago, I'm pretty certain the server would just throw an unhandled error inside that callback function, so bringing this up to spec shouldn't be a big deal. I vote patch release.

@kherock kherock deleted the fix-372 branch November 4, 2019 01:40
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