Paginator

Table footer control for offset/limit queries.

Bind offset and limit to your fetch Resource, set total_count from Page::total_count, and page clicks update offset automatically. When total_count is unknown, navigation collapses to a single page. Renders core Pagination for the page-button UX.

  • Table and list views with explicit page controls and a known (or eventually known) total
  • Platform paging convention: offset + limit rather than page index in your query layer

Prefer crate::components::OrbitalInfiniteScroll when load-more-on-scroll fits better — social feeds, activity logs, and long catalogs where scrolling is the primary navigation. Use crate::components::EmptyState when the first page returns no items.

  • Create an offset signal (starts at 0).
  • Pass limit matching your query page size.
  • Set total_count from the first page response (Page::total_count).
  • Bind the table Resource to offset so page clicks trigger a refetch.

Renders native Pagination from orbital-core-components.

Minimal wiring (docs snippet — not a live preview):

Default pagination

Table footer with 25 rows per page and a known total.

...
Small dataset (3 pages)

Compact footer with ten rows per page and thirty total items, yielding three page buttons. Use to verify pagination layout and behavior on short lists without many controls.

Unknown total

Single-page fallback when the server has not returned a total yet.

Click page 2 updates offset

Paginator bound to an offset signal with a live readout of the current offset value. Use to confirm page clicks write back to the parent offset for Resource refetches.

0
Theme surfaces

Active page button resolves theme tokens.