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

Added support for paged results #17

Merged
merged 9 commits into from
Sep 3, 2015
Merged

Added support for paged results #17

merged 9 commits into from
Sep 3, 2015

Conversation

JSkimming
Copy link
Owner

Methods like List zones and List DNS Records have a maximum number of entries they will return in a single request, and use paging to return more records.

To handle this the library now exposes the paged results in the API, which has resulted in breaking change.

Helper methods GetAll[Zones|DnsRecords]Async are also provided that still return the complete list and will make multiple requests if necessary.

To remove ambiguity as to their function.
Previously it returned the list of zones, but it needs to return the
whole response to expose access to the pagination information.
Previously it returned the list of DNS records, but it needs to return
the whole response to expose access to the pagination information.
These can involve multiple paged requests.
JSkimming added a commit that referenced this pull request Sep 3, 2015
Added support for paged results
@JSkimming JSkimming merged commit 523a2ed into master Sep 3, 2015
@JSkimming JSkimming deleted the paged-results branch September 3, 2015 08:33
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.

1 participant