Translating the requirement: it'd be convenient to allow PagedIterator to skip forward without actually retrieving the objects in between.

I think the PageIterator simply needs to implement the "page" parameter to skip to a particular page. It support size but not page from what I can tell.

https://developer.github.com/v3/#pagination

@nodoze
Yes, there is enough information for PagedIterable to know how many pages it has, you only have get the first page in order to know the total number of pages. Seems like something that could be added without breaking anything.

In #448, another scenario was mentioned - restarting a search from a specific page. One thing to keep in mind for searches is that the underlying data may have changed. At that point the page position of items may have changed. This a generally problem for any paged query though, so maybe that is something that we can leave to consumers of the API to figure out for themselves.

I think it would make sense to add a GitHubPaginator class that handles page traversal and navigation. PagedIterable would have a method paginator() that would return the new class and support going to a specific page, next, previous, etc.

See #1197
Other users would like a method that returns an iterator that only returns results for a specific page range: pageRange(start, end). Results would be returned only within that page range.

I'm thinking the following methods on the iterable:
startAtPage(long)
endAfterPage(long)
pageRange(long, long)
pageIterator()
pageIterator(start_page)
pageIterator(start_page, end_page)

And adding methods to the iterator and page iterator:
hasPrevious()
previous()
getCurrentPageNumber()
getPageCount()
first()
last()

@bitwiseman Hey! Thank you for this library, works great! I ended up not using this library for integrating with the paginated GitHub APIs because of the lack of support for specific page number, and wrote my own simple client instead.

I'd like to implement this, perhaps starting with these new methods in PagedIterator, using just the Link response header, then moving to the other features that would use the page param.

hasPrevious() previous() getCurrentPageNumber() getPageCount() first() last()

Any updates to the design you thought of in the previous comments, about the new class GitHubPaginator that is accessible from PagedIterator? Looks fine to me, just wanted to confirm given that it has been more than 2 years since the comments.

Thanks,
Anuj

Please go ahead.

Hey, could I have access to hub4j-test-org organization for testing?

I have implemented two new classes Paginator and GitHubPaginator analogous to PagedIterator and GitHubPageIterator respectively, accessible from PagedIterable. I have kept PagedIterator and GitHubPageIterator as they were.

We can have a discussion when I raise the PR for this, testing in progress.

@anujhydrabadi
Invitation sent for test org.

This is some additional documentation in this area:
https://docs.github.com/en/rest/guides/using-pagination-in-the-rest-api?apiVersion=2022-11-28