Repository navigation
Pagination #161
Description
Activity
Yeah, as the pagination data is not exposed in the response body, you won't have the information available.
We could perhaps add an option to output the pagination data as JSON before or after the response body on stdout, however that would pose a problem of parsing, as it's not a single JSON document any more.
Thanks jablan. For some inspiration you could take a look at the GitHub CLI's
--paginateand--slurpoptions -- https://cli.github.com/manual/gh_apiI see. As a workaround measure, you can iterate by increasing
pageparameter until there's no more results left in the response.
How do you use pagination with the CLI? There's no way to access a response's Link/Pagination HTTP headers.
For example, I need to get a list of 500 keys in my project.
phrase keys list --project_id 123xyz --batchreturns the first 25. How do I know there are 475 left?