You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way of traversing with Pagination as explained here? I could not find anything in the docs or code
So far, the only way I could find to do it is to look at the link header in the response headers. But seems a very complicated way to do it, since all tags are shown as a single string:
Link | <https://api.github.com/organizations/9919/members?page=1&per_page=1>; rel="prev", <https://api.github.com/organizations/9919/members?page=3&per_page=1>; rel="next", <https://api.github.com/organizations/9919/members?page=214&per_page=1>; rel="last", <https://api.github.com/organizations/9919/members?page=1&per_page=1>; rel="first"
The text was updated successfully, but these errors were encountered:
@BenFradet Your solution has two issues. First, by enumerating the pages beforehand, it may fail due to changes in number of pages. Open PRs filter might find itself fetching a page that does not exist, and there's always the risk of fetching too few pages.
The second is that github API documentation repeatedly emphasizes that one must not construct the URL, but use the one given. The inability to do that is a flaw on github4s API.
Is there a way of traversing with Pagination as explained here? I could not find anything in the docs or code
So far, the only way I could find to do it is to look at the
link
header in the response headers. But seems a very complicated way to do it, since all tags are shown as a single string:The text was updated successfully, but these errors were encountered: