facebook / facebook/astryx

Table: server-driven pagination

Open
#5,472 0 comments 0 reactions 1 assignee Claimed by @humbertovirtudes View on GitHub
enhancement
Dominant language
TypeScript
Stars
13.1k
Forks
1.1k
Avg merge
1d 14h
Merged PRs (30d)
669

Description

Part of the Table feature suite tracker #3639.

**Feature area:** Rendering & performance / data source

### Problem

Astryx core `Table` only has offset-based `useTablePagination`, which paginates a client-held data array. The EPS table has **server-driven pagination** (EPS `useEPSTableServerPagination`): the table renders only the current page's rows while the server owns total count, page size, and page fetching.

### Scope

- A `useTableServerPagination` plugin (or mode) where the consumer supplies `{pageIndex, pageSize, totalCount, onPageChange}` and the table renders the given page slice without holding the full dataset.
- Loading state during page fetch (composes with the loading-state work #3964).
- Decide plugin vs. mode of `useTablePagination` (API arbitration here).

_Surfaced from the EPS -> Astryx plugin audit: EPS has Cursor / Server / Relay pagination variants; Astryx only has basic offset paging._

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.