Turning the Page! In tutorial 2, we'll control how many items Graph returns on each Page of results and retrieve specific Pages.
When GraphQL returns results, it will organise them into pages. This allows it to be more efficient, as it only returns the data that is needed straight away. At the same time, the rest of the pages are organised ready for the next request.
You'll always need to think about Pagination when using GraphQL, even you only want to retrieve the first Page of results.
per page is an argument used to define the number of results that will be returned on each page.
It's now a mandatory argument on some types of query so we've already got the argument in our query from the last tutorial:
Experiment by changing the integer in the argument from 20 to another value. Observe the difference. It's recommended to keep the per_page number as low as possible- for efficiency and performance.
Let's consider a few situations:
You can return pagination metadata alongside your query results:
These optional properties can be requested alongside total_entries and your results object, like in the example below. Try them out. Code:
You can view other pages by setting the page argument to the page of results you'd like to see. Code:
In the next Article, we'll look at how to filter results.
For example, we'll learn how to return items from only a specific WebApp.