What problem does it solve?
Deciding whether filtering, sorting, grouping, expanding, or pagination should run on the client or the server in TanStack Table v9 is error-prone: misused manual* flags cause unsorted pages, double-processing, or render loops. This Skill clarifies which dataset each row-model stage receives and how to wire manual modes correctly.
Core Features & Use Cases
- Ownership decision guidance: Explains when the client owns the full pipeline versus when the server owns processing with manualFiltering, manualSorting, and manualPagination flags.
- Server-side patterns: Shows how to pass controlled filter, sorting, and pagination state into request/query keys and supply rowCount for server totals.
- Common mistake prevention: Documents critical errors like treating manual flags as data-fetching requests, expecting manual pagination to slice data, sorting only the loaded page, and recreating data or columns inline.
- Use Case: You are building a React datagrid backed by a paginated API with 12,000 rows. Use this Skill to configure manualPagination and manualSorting correctly so the table renders server-fetched pages without re-sorting only the visible slice.
Quick Start
Ask the AI to configure TanStack Table so that sorting and pagination are handled by the server while the table renders the fetched page with the correct rowCount.