Pagination

With Pagination you can limit the number of documents returned per page, and get a specific page of results. This is useful for creating paginated lists of documents within your application. All paginated responses include documents nested within a docs array, and return top-level meta data related to pagination such as totalDocs, limit, totalPages, page, and more.

Collection find queries are paginated automatically.

Options

All FrogBot APIs support the pagination controls below. With them, you can create paginated lists of documents within your application:

Control	Type	Default	Description
`limit`	`number`	`10`	Limits the number of documents returned per page. More details.
`pagination`	`boolean`	`true`	Set to `false` to disable pagination and return all documents.
`page`	`number`	`1`	Get a specific page number.

Local API

To specify pagination controls in the Local API, you can use the limit, page, and pagination options in your query:

import type { FrogBot } from 'frogbot'

const getPosts = async (frogbot: FrogBot) => {
  const posts = await frogbot.find({
    collection: 'posts',
    overrideAccess: true,
    limit: 10,
    page: 2,
  })

  return posts
}

REST API

With the REST API, you can use the pagination controls below as query strings:

fetch('https://localhost:3000/api/posts?limit=10&page=2')
  .then((res) => res.json())
  .then((data) => console.log(data))

Response

All paginated responses include documents nested within a docs array, and return top-level meta data related to pagination. The find operation includes the following properties in its response:

Property	Type	Description
`docs`	`T[]`	Array of documents in the collection
`totalDocs`	`number`	Total available documents within the collection
`limit`	`number`	Limit query parameter - defaults to `10`
`totalPages`	`number`	Total pages available, based upon the `limit` queried for
`page`	`number`	Current page number
`pagingCounter`	`number`	`number` of the first doc on the current page
`hasPrevPage`	`boolean`	`true/false` if previous page exists
`hasNextPage`	`boolean`	`true/false` if next page exists
`prevPage`	`number \| null`	`number` of previous page, `null` if it doesn’t exist
`nextPage`	`number \| null`	`number` of next page, `null` if it doesn’t exist

Example response:

{
  "docs": [
    {
      "title": "Page Title",
      "description": "Some description text",
      "priority": 1,
      "createdAt": "2020-10-17T01:19:29.858Z",
      "updatedAt": "2020-10-17T01:19:29.858Z",
      "id": "5f8a46a1dd05db75c3c64760"
    }
  ],
  "totalDocs": 6,
  "limit": 1,
  "totalPages": 6,
  "page": 1,
  "pagingCounter": 1,
  "hasPrevPage": false,
  "hasNextPage": true,
  "prevPage": null,
  "nextPage": 2
}

Limit

You can specify a limit to restrict the number of documents returned per page.

By default, any query with limit: 0 will automatically disable pagination.

Performance benefits

If you are querying for a specific document and can reliably expect only one document to match, you can set a limit of 1 (or another low number) to reduce the number of database lookups and improve performance. For example, when querying a document by a unique field such as slug, you can set the limit to 1 since you know there will only be one document with that slug. To do this, set the limit option in your query:

await frogbot.find({
  collection: 'posts',
  overrideAccess: true,
  where: {
    slug: {
      equals: 'post-1',
    },
  },
  limit: 1,
})

Disabling pagination

Disabling pagination can improve performance by reducing the overhead of pagination calculations and improve query speed. For find operations within the Local API, you can disable pagination to retrieve all documents from a collection by passing pagination: false to the find local operation. To do this, set pagination: false in your query:

import type { FrogBot } from 'frogbot'

const getPost = async (frogbot: FrogBot) => {
  const posts = await frogbot.find({
    collection: 'posts',
    overrideAccess: true,
    where: {
      title: { equals: 'My Post' },
    },
    pagination: false,
  })

  return posts
}

Start here

Basics

Managing Data

Features

Ecosystem

Deployment

Options

Local API

REST API

Response

Limit

Performance benefits

​Options

​Local API

​REST API

​Response

​Limit

​Performance benefits

​Disabling pagination

Options

Local API

REST API

Response

Limit

Performance benefits

Disabling pagination