solid/table-state

What problem does it solve?

It solves the confusion and bugs caused by misunderstanding how TanStack Table state works in Solid, especially around reactive getters and the fact that table.state is an accessor that must be called.

Core Features & Use Cases

• Correctly wire Solid reactivity into createTable by using reactive getters for options like data, so the table recomputes when upstream signals change.
• Read table state properly with table.state() to access pagination, sorting, filtering, and other slices as Solid accessors, not as direct values.
• Choose the right state ownership model using initialState, state/on*Change (signal-backed), or external atoms via @tanstack/solid-store for shared state across components.
• Render with FlexRender and optionally createTableHook to standardize table components and conventions across an app, including header/cell rendering patterns.

Quick Start

Use the solid/table-state skill to correctly implement createTable with reactive getters, read state via table.state().<slice>, and optionally connect shared slices with @tanstack/solid-store selectors.