-
Notifications
You must be signed in to change notification settings - Fork 772
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
Note on limit
param in autoPagingToArray
#2074
Note on limit
param in autoPagingToArray
#2074
Conversation
Makes it more explicit that the `limit` value passed to `autoPagingToArray` is the limit for the total number of items that will be fetched from Stripe, and not a limit for the number of items retrieved per fetch during multiple rounds of fetching.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Sorry for the confusion here.
Also added some comments to the code snippet below to hopefully clarify even further.
* Note on `limit` param in `autoPagingToArray` Makes it more explicit that the `limit` value passed to `autoPagingToArray` is the limit for the total number of items that will be fetched from Stripe, and not a limit for the number of items retrieved per fetch during multiple rounds of fetching. * Update README.md --------- Co-authored-by: Richard Marmorstein <[email protected]>
* Note on `limit` param in `autoPagingToArray` Makes it more explicit that the `limit` value passed to `autoPagingToArray` is the limit for the total number of items that will be fetched from Stripe, and not a limit for the number of items retrieved per fetch during multiple rounds of fetching. * Update README.md --------- Co-authored-by: Richard Marmorstein <[email protected]>
This change to the
README.md
file makes it more explicit that thelimit
value passed toautoPagingToArray
is the limit for the total number of items that will be fetched from Stripe, and not a limit for the number of items retrieved per fetch during multiple rounds of fetching. The note about preventing runaway memory growth was suggestive of this behavior, but not entirely explicit.