-
Notifications
You must be signed in to change notification settings - Fork 238
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
List* methods should not be paginated by default; create paginated versions #295
Comments
Others to fix: Lines 142 to 154 in 77a73c9
Lines 265 to 278 in 77a73c9
|
is there any way when using the cli to specify we want more than 25 results?
|
No, but I did see another issue asking for that feature to be added.... |
In v1 of the API we do not disambiguate between methods that do the pagination for us, and those that do it on our behalf. A good example is
ListBusinessServices()
.For v2 we should probably update
ListBusinessServices()
to not automatically do pagination, and create aListBusinessServicesPaginated()
version instead.We should probably adopt this naming scheme in v1 for anything that we add that is going to do pagination on the behalf of the user. One example of us already doing this:
go-pagerduty/service.go
Line 125 in 1a0c44e
The text was updated successfully, but these errors were encountered: