release: data-table-pro v5.0.0 - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
@tanstack/react-tablefrom v8.21.3 to v9.1.2.useReactTablewithuseTableand register the table features, row models, and function registries explicitly.left/rightpinning contract for props, persistence, saved views, URL state, and API snapshots.Why
TanStack React Table v9 changes table construction, feature registration, type generics, state access, sorting and aggregation APIs, pinning terminology, and instance method behavior. This major release adopts those APIs directly without the deprecated legacy bridge.
Consumer impact
Direct TanStack-facing column definitions and table-instance code must follow the documented v9 migration. The component-level
DataTablestate API, existing package entrypoints, persisted state, saved views, URL-state formats, and physicalleft/rightpinning contract remain supported.Validation
distoutput and current public API snapshot