Hey there, we got pagination working in a nice way. We mentioned we were working on it here: #14
In your query string, you can specify ?page=1&page_size=250. The response will then be paginated to the first 250 results.
We have hardcoded id to be descending, so it's always newest to oldest. Let us know if this is ok, there is currently no user ordering option in Kalamata.
If you leave page blank, nothing will happen. It's required.
If you leave page_size blank, it will default to 100. Supplying page_size without page will also do nothing
If you set page_size to 99999 or something greater than the total pages, it will just return the full list on one page.
We took a leaf out of Wordpress wp-json's book for defining the next pages.
In this example, we'll query our API with /users?where={"type":"CUSTOMER"}&page=2&page_size=250.
In the response headers, you will get the following:
When you reach the first or last page, x-prev or x-next will be accordingly undefined. This is how you know you've reached the boundaries of the page list.
Would appreciate any feedback. We also bumped the version to 0.2 as although everything should continue working as normal for existing people not using ?page= there were some architecture changes and a new node module for query string manipulation.
Hey there, we got pagination working in a nice way. We mentioned we were working on it here: #14
In your query string, you can specify
?page=1&page_size=250
. The response will then be paginated to the first 250 results.We have hardcoded id to be descending, so it's always newest to oldest. Let us know if this is ok, there is currently no user ordering option in Kalamata.
If you leave
page
blank, nothing will happen. It's required. If you leavepage_size
blank, it will default to 100. Supplyingpage_size
withoutpage
will also do nothing If you setpage_size
to 99999 or something greater than the total pages, it will just return the full list on one page.We took a leaf out of Wordpress
wp-json
's book for defining the next pages.In this example, we'll query our API with
/users?where={"type":"CUSTOMER"}&page=2&page_size=250
.In the response headers, you will get the following:
/users?where={"type":"CUSTOMER"}&page=3&page_size=250
/users?where={"type":"CUSTOMER"}&page=1&page_size=250
43
10610
When you reach the first or last page,
x-prev
orx-next
will be accordingly undefined. This is how you know you've reached the boundaries of the page list.Would appreciate any feedback. We also bumped the version to 0.2 as although everything should continue working as normal for existing people not using
?page=
there were some architecture changes and a new node module for query string manipulation.