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

Clarify language around "max" CLI flags #38

Merged
merged 3 commits into from
Oct 16, 2018
Merged

Conversation

jrmontag
Copy link
Collaborator

I've attempted to be more explicit and consistent with the language used to explain and differentiate between the two CLI flags: --max-results and --results-per-call. These are understandably a bit confusing and #37 reminded me that we could try to be more specific.

I've attempted to be more explicit and consistent with the language used to explain and differentiate between the two CLI flags: ``--max-results`` and ``--results-per-call``. These are understandably a bit confusing and #37 reminded me that we could try to be more specific.
@jrmontag jrmontag requested a review from binaryaaron June 29, 2018 16:06
Copy link
Contributor

@binaryaaron binaryaaron left a comment

Choose a reason for hiding this comment

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

I'm tagging @EmilySheehan here as we discussed changing results-per-call and max-results of these to not be overloaded with the search API at all, but I like adding the explicit notice here. Thanks!

Copy link
Contributor

@binaryaaron binaryaaron left a comment

Choose a reason for hiding this comment

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

Whoops, I made a mistake - these changes should go into the examples/base_readme.rst file, as this readme is generated from there. @jrmontag, do you mind putting this verbiage into that file?

@jrmontag
Copy link
Collaborator Author

jrmontag commented Jul 3, 2018

Thanks for the clarification, and no problem. I'll make those changes and add another commit.

@binaryaaron
Copy link
Contributor

Perhaps we can roll #39 into this? How would you feel about that, @jrmontag? We can also do that in a different PR.

@jrmontag
Copy link
Collaborator Author

@binaryaaron I've reverted that change and move the text into the correct file. Let me know if you'd like to see any other changes.

@jeffakolb
Copy link
Collaborator

@jrmontag @binaryaaron could you guys follow up on this?

@binaryaaron binaryaaron merged commit da5afeb into master Oct 16, 2018
@binaryaaron binaryaaron deleted the jrmontag-maxresults branch October 16, 2018 16:13
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.

3 participants