What problem does it solve?
Managing TanStack Table state in Angular is error-prone: developers must decide who owns each state slice, handle value-or-updater callbacks correctly, and avoid performance issues caused by injectTable initializer reruns when signals change.
Core Features & Use Cases
- State Ownership Patterns: Choose between internal state, initialState, external @tanstack/angular-store atoms, or controlled Angular signals for each state slice.
- Signal Integration: Read table.atoms directly in templates, computed, and effect with automatic Angular signal tracking.
- Updater Resolution: Correctly handle value-or-updater callbacks in onPaginationChange and similar handlers without corrupting state.
- Use Case: You are building an Angular datagrid whose pagination state must sync with a query cache. Create a stable atom with createAtom from @tanstack/angular-store, pass it via the atoms option, and let table APIs update it without rerunning the injectTable initializer.
Quick Start
Show me how to control TanStack Table pagination state in my Angular component using a signal and the onPaginationChange callback.