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
Pagination details on contents API missing #334
Labels
Comments
@nilslice ^ does that make sense? |
That does make sense, feel free to send the PR. I'll try to get this and your other PR merged by the weekend. Been busy wrapping up 2019! Happy new year! |
Happy new year, thanks!!! :)
Enviado desde mi iPhone
… El 1 ene 2020, a las 22:58, Steve Manuel ***@***.***> escribió:
That does make sense, feel free to send the PR. I'll try to get this and your other PR merged by the weekend. Been busy wrapping up 2019! Happy new year!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The GET /api/contents?type= request provides the capability to request by offset/count. But it's impossible to determine how many items exist in the database.
Such information would be helpful to implement pagination on the frontends.
I suggest to implement a "total_count" (or any similar name on the response).
I can send a PR for that.
The text was updated successfully, but these errors were encountered: