Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

s/max_keys/max-keys/ when parsing url query parameters #64

Merged
merged 1 commit into from
Sep 8, 2016

Conversation

mpl
Copy link
Contributor

@mpl mpl commented Sep 1, 2014

According to http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGET.html , the parameter is max-keys, not max_keys.
You need the conversion to an int as well, since you're gonna use max_keys as an int in the rest of the code. But I'm no rubyist, so I don't know if that conversion is idiomatic.

According to http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGET.html , the parameter is max-keys, not max_keys.
You need the conversion to an int as well, since you're gonna use max_keys as in int in the rest of the code. But I'm no rubyist, so I don't know if that conversion is idiomatic.
eikevons pushed a commit to eikevons/fake-s3 that referenced this pull request Aug 26, 2015
uberjay added a commit to uberjay/fake-s3 that referenced this pull request Aug 3, 2016
@pickhardt
Copy link
Collaborator

You can just use "13".to_i to convert a string to an int. But thanks, I will merge this.

@pickhardt pickhardt merged commit 7f0d899 into jubos:master Sep 8, 2016
@pickhardt
Copy link
Collaborator

Actually, why converting it to an int, then back to a string? That seems strange. I am removing that.

@pickhardt
Copy link
Collaborator

Thanks for the PR but I'm going to have to change your commit. The tests are breaking and I need to fix them.

@pickhardt
Copy link
Collaborator

OK, I have fixed the change now. The max-keys should work right.

@mpl
Copy link
Contributor Author

mpl commented Sep 8, 2016

@pickhardt thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants