-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Response pageCount is incorrect #1813
Comments
aler9
added a commit
that referenced
this issue
May 18, 2023
aler9
added a commit
that referenced
this issue
May 18, 2023
aler9
added a commit
that referenced
this issue
May 18, 2023
aler9
added a commit
that referenced
this issue
May 18, 2023
Hello @tbnguyen1407 , thanks for reporting the two issues. I fixed the |
Fixed in in v0.23.1 |
This issue is being locked automatically because it has been closed for more than 6 months. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which version are you using?
v0.23.0
Which operating system are you using?
Describe the issue
Page count is incorrect when
itemsPerPage
is smaller or equal to total number of itemsDescribe how to replicate the issue
/v1/paths/list?itemsPerPage=X
Did you attach the server logs?
no
Did you attach a network dump?
no
Notes
For pagination it is more common to return total item count instead of total page count and let the client side figure out the total page count. It is currently not possible to know how many paths there are in total.
Client side needs:
Common practice is to return pagination in response header, e.g.:
The text was updated successfully, but these errors were encountered: