Closed MalteHerrmann closed 3 months ago
I am having the same problem with the RepoHandler
.
Thank you for your issue! I don't currently have time to investigate a fix myself but I'm happy to review a PR addressing the issue. 🙂
I was looking into a potential "fix" and realised that I was just misunderstanding the purpose of these fields. It works just fine according to the behavior of the GitHub API - for reference if anyone else is confused by this:
total_count
is not reported by the GitHub API for these kinds of requestsnext
, prev
, last
, and first
fields will be noneThese were the assumptions I did not know of - in other cases the fields are filled as expected.
Problem
The returned
Page<...>
instances from e.g. theReleasesHandler
orPullRequestHandler
have pretty much all of their fields set toNone
values, even though the objects like releases or pull requests could be successfully retrieved. Since there wereitems
returned, I would expect thenext
, andfirst
fields to work as well as thetotalCount
.How To Reproduce
The following test showcases this.