01
Overview
Page-navigation control for stepping through multi-page result sets.
Usage
When the total page count is unknown, omit totalPages and pass the direction
availability you know:
This renders the current page and previous/next controls without implying a fake final page.
REST Link headers
Cursor pagination
02
When to use
Use when
- Moving through a large, ordered dataset split into discrete pages of fixed size.
- Showing the current page in context of the total page count.
Avoid when
- Switching between named sibling views — use tabs instead.
- Streaming results as the user scrolls — wire up infinite scroll directly.
03
Examples
Basic pagination
Navigate through pages with previous/next and numbered buttons.
Cursor pagination
Use page-local cursor metadata when an API exposes previous and next cursors instead of totals.
REST Link-header pagination
Drive previous and next buttons from parsed REST Link headers without a total page count.
Pagination with total count
totalCount prop shows formatted record count.
04
Props
| Name | Type | Default | Required | Bindable | Description |
|---|---|---|---|---|---|
currentPage | number | 1 | bind | Current page number (1-indexed). Bindable. | |
totalPages | number | Total number of pages. Omit when only previous/next availability is known. | |||
hasPreviousPage | boolean | Whether a previous page is available when totalPages is unknown. Defaults to currentPage > 1. | |||
hasNextPage | boolean | false | Whether a next page is available when totalPages is unknown. Defaults to false. | ||
totalCount | number | Optional total record count; formatted with formatNumber when provided. |