0
Fork 0
mirror of https://github.com/TanStack/table.git synced 2026-11-18 18:55:54 +00:00
Commit graph

77 commits

Author SHA1 Message Date
Kevin Van Cott
87c6bcc52a
feat(table-core): Further improve tree-shaking across features (#6626)
* feat(table-core): Further improve tree-shaking across features

Keep column ordering, column pinning, and row expanding code out of the
core bundle, route more cross-feature reads through feature stubs, and
stop allocating unused onAfterUpdate wrappers in production memos.

* refactor(table-core): register internal cross-feature fns as table APIs

Replace init*InstanceData function storage with @internal table APIs
registered via assignTableAPIs, route faceting through the
getCanGlobalFilter stub, and enforce feature boundaries with
import/no-restricted-paths. Regenerate reference docs and fix stale
docs config links.

---------
2026-10-12 09:51:47 -05:00
Kevin Van Cott
4533d1f45a
docs: grammar pass 2026-08-18 08:53:46 -05:00
Fabian Iwand
ba704b4b13
docs: Fix callout formatting (#6549)
* Fix callout formatting

* docs: convert remaining blockquote callouts to GitHub alert syntax

Converts all 341 remaining old-style callouts (> **Note:**, > NOTE:,
> **NOTE**:, > Tip:, > **Warning:**, etc.) across the docs to the
GitHub markdown alert syntax ([!NOTE], [!TIP], [!WARNING], [!IMPORTANT])
that tanstack.com renders as styled callouts.

Also fixes one pre-existing alert in client-side-vs-server-side.md that
had its content on the same line as the marker, and trailing whitespace
on the alert marker in the svelte quick-start.

Qualified callouts with custom titles (TypeScript Note, Framework note,
Naming note) are intentionally left as plain blockquotes since the alert
syntax does not support custom titles.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Kevin Van Cott <kevinvandy656@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-08-13 09:05:20 -05:00
Kevin Van Cott
8b60ea1f89
docs: add esm only build info to migration guides 2026-08-11 07:44:00 -05:00
Kevin Van Cott
09598d2e41
feat: support infinite pagination page sizes (#6526)
* feat: support infinite pagination page sizes

* add devtools to all with-tanstack examples

* ci: apply automated fixes

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-08-07 13:11:04 -05:00
Kevin Van Cott
a15c9e6fd6
docs: update client vs server guide and tanstack query examples 2026-08-07 10:23:29 -05:00
Kevin Van Cott
50feff8584
docs: clean up migration guides 2026-08-04 10:49:17 -05:00
Kevin Van Cott
2327f80906
release v9 (#6512)
* release v9

* update docs for v9 stable

* ci: apply automated fixes

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-08-04 00:22:59 -05:00
Kevin Van Cott
c6e8a34390
fix: correct row behavior and expand feature guides (#6509) 2026-08-03 21:15:24 -05:00
Kevin Van Cott
82c32e0bc6
docs: regen docs and fix some typos repo wide 2026-08-03 07:31:20 -05:00
Kevin Van Cott
8fcfd34531
fix(table-core): correct number-range, filter-depth, autoRemove, and custom faceting semantics (#6503)
* fix(table-core): correct number-range, filter-depth, autoRemove, and custom faceting semantics

Four filtering-semantics bugs from the beta triage.

filterFn_inNumberRange matched non-numeric values: JavaScript's loose
relational coercion let null, '', and booleans slip into a numeric range
(null >= 0 && null <= 20 is true), so the auto-selected number filter
leaked empty rows into a [0, max] range on nullable numeric columns. The
filter now only matches real numbers. Numeric strings also stop
matching; `between`/`betweenInclusive` remain the hybrid string/number
range filters.

When maxLeafRowFilterDepth stopped the root-down filter recursion, the
kept rows' unfiltered descendants stayed visible through row.subRows but
never entered flatRows or rowsById, so facet counts and other
flat-representation consumers under-counted after filtering. Truncated
subtrees now join both. Scoped to the root-down path; the leaf-up path
drops truncated subRows entirely (pre-existing behavior) and is left as
a possible follow-up.

shouldAutoRemoveFilter ORed a hardcoded empty-string check over a custom
autoRemove, so a filter function that wanted to keep '' as a filter
value could not. A provided autoRemove is now authoritative for defined
values; undefined always clears, since it is the universal
setFilterValue(undefined) sentinel. Built-ins are unaffected: they all
test falsy values themselves.

Custom facetedUniqueValues/facetedMinMaxValues/facetedRowModel factories
were frozen by a redundant memoization layer in columnFacetingFeature.
The stock factories already memoize internally with the same
dependencies, so the API-layer memoDeps only served to cache custom
implementations against inputs they do not depend on. The API layer is
now a plain pass-through like every other row model: stock results stay
referentially stable and compute once per invalidation (pinned by
Map-identity tests), the no-factory fallback keeps a stable empty Map,
and custom factories own their memoization (tableMemo is exported for
this). The faceting guides now document the contract and their
server-side examples read live data through table.options.meta instead
of stale closures.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(table-core): read live facet data in remaining server-side faceting examples

The alpine, ember, lit, and octane guides captured a one-time `await fetch`
result in the factory closure, so later server responses could never reach
either faceting API. They now read through `table.options.meta` inside the
returned functions like the other framework guides, using each framework's
own reactive idiom.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-08-02 23:14:07 -05:00
Kevin Van Cott
aad2c292cb
fix(table-core): correct expanded/paginated state contents and sorting toggle defaults (#6501)
Two independent clusters of default-behavior bugs from the beta triage.

Expanded and paginated state contents:

Expand-all materialized every id in `rowsById`, including leaf rows that
can never expand, so a serialized `ExpandedState` was polluted with dead
keys and `getExpandedDepth` was skewed by them. Materialization now writes
only ids where `row.getCanExpand()` is true, chosen over `subRows.length`
so `getRowCanExpand` lazy-load overrides stay expandable.
`getExpandedDepth` filters the same way, and `getIsAllRowsExpanded` now
only considers expandable rows so the materialized map still round-trips
as "all expanded" (a map of stale ids with no expandable rows is false).

Paginated `flatRows` pushed each row and then recursed into its subRows,
but page rows already contain expanded descendants inline, so those rows
appeared twice. The rebuild now dedupes by row id. Collapsed descendants
stay included, consistent with every other row model, where `flatRows`
ignores expansion state.

`row.toggleExpanded(bool)` and `table.toggleAllRowsExpanded(bool)` fired
`onExpandedChange` even when the requested state already matched, so
controlled consumers got spurious callbacks. Both now early-return.

Neither toggle consulted `row.getCanExpand()`, unlike their row-selection
equivalents, so a non-expandable row could be written into expanded state
imperatively. The expand direction is now guarded; collapsing is always
allowed so stale expanded ids can still be cleaned up.

Sorting toggle defaults:

`column.toggleSorting()` called `column.getNextSortingOrder(column)` with
no `multi` argument, so `enableMultiRemove` was dead on every path. The
argument is now forwarded as `multi && column.getCanMultiSort()`, matching
the multi-mode condition the updater itself uses. The public
`getNextSortingOrder` type now accepts the `multi` argument it always
supported at runtime.

`column.getAutoSortDir()` sampled only `flatRows[0]`, so a leading null or
a manual-sorting data swap flipped the inferred first direction mid-cycle
and silently dropped a state from the toggle cycle. It now samples the
first 10 rows for a non-nullish value, matching `getAutoSortFn`.

Docs: `sortUndefined: false` was documented as "considered tied" in all
framework sorting guides; undefined values are actually passed straight to
the sorting function with no special handling. Corrected, and the missing
`'first'`/`'last'` bullets were added to the generated reference.

Also fixes three crashes in the MRT examples surfaced while testing the
sorting changes. The MUI and Mantine sort labels read `sorting` off
`state`, which does not carry it, and crashed on `sorting.length`; they now
read it through `table.Subscribe` on `table.atoms.sorting`, which also
makes the badge reactive. The row-action edit handler passed a shallow row
copy to `setEditingRow`, breaking the row identity the edit modal needs.
`mrtRefsFeature` seeded the keyed `editInputRefs`/`filterInputRefs` bags
with `null` instead of `{}`, crashing on first keyed write. New e2e
coverage pins all three plus the sort-direction indicator.

Closes #6115
Closes #5833
Closes #6136
Closes #4939
Closes #4946
Closes #5147
Closes #5832

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-02 22:19:11 -05:00
Kevin Van Cott
0c57cc8b0e
fix: honor selection rules in select-all paths, add deselectParents option (#6495)
* fix: honor selection rules in select-all paths, add deselectParents option

Three coordinated row selection fixes for the v9 beta window:

- toggleAllRowsSelected and the getIsAllRowsSelected/getIsAllPageRowsSelected
  getters now honor enableSubRowSelection: sub-rows whose ancestors block
  descent are skipped by select-all and excluded from the all-selected
  computation, matching what toggleAllPageRowsSelected already did (#5116)
- deselecting all rows now preserves the selection of rows whose
  enableRowSelection resolves false; deselectAll: true and
  resetRowSelection(true) remain the full-clear escapes (#5398)
- new opt-in deselectParents flag on ToggleSelectedOptions removes ancestor
  row ids from the selection when a row is deselected, covering the
  select-parent-then-deselect-child sequence without changing default state
  semantics (#6049)

Eligibility walks are deduped with a per-pass ancestor cache (the
enableSubRowSelection predicate runs once per unique parent), and the
all-selected scans check the cheap isRowSelected lookup first so selected
rows skip capability checks entirely.

Includes 20 new tests, updated row-selection guides for all 10 frameworks
(the canonical checkbox snippet now shows the nested-data pattern), SKILL
updates, and refreshed triage notes.

Fixes #5116
Fixes #5398
Fixes #6049
Fixes #4878
Fixes #5416

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* docs(table-core): lock in deselectParents pruning contract for non-selectable ancestors

Review feedback suggested gating pruneAncestorRowIds on row_getCanSelect. That
would reintroduce the stale-parent state the opt-in exists to remove: a
skipped non-selectable ancestor keeps reporting getIsSelected() over a
deselected child. The enableRowSelection deselect guard is deliberately scoped
to the bulk select-all paths only; targeted deselection paths, including
pruning, may clear any id. Encode the decision in JSDoc, an implementation
comment, and a regression test.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-08-02 10:31:23 -05:00
Kevin Van Cott
34ad4676ff
feat: add opt-in sorting auto-reset (#6489)
Co-authored-by: Jiajun Chen <tychenjiajun@live.cn>
2026-08-01 21:09:05 -05:00
Kevin Van Cott
e2f305df76
feat: rowSpan and colSpan for cells (#6487)
* feat: rowSpan and colSpan for cells

* address feedback
2026-08-01 19:31:54 -05:00
Kevin Van Cott
0b294316dc
feat: support subtractive cell selection (#6476)
* feat: support subtractive cell selection

* ci: apply automated fixes

* ci: apply automated fixes (attempt 2/3)

* ci: apply automated fixes (attempt 3/3)

* docs: update cell selection skills

* vite type module

* remove test results

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-08-01 07:28:44 -05:00
Kevin Van Cott
f944d5893e
chore: package upgrades 2026-07-31 17:40:00 -05:00
Kevin Van Cott
d2b2f75d45
feat: octane-table adapter (#6477)
* feat: octane-table adapter

* add skills for octane

* move to compiled tsrx
2026-07-31 14:44:13 -05:00
Riccardo Perra
4be42f940d
fix: react adapter sync state (#6458)
* fix: react adapter sync state

* Some changes

* refactor: move render-phase sync strategy into core reactivity bindings (#6459)

* refactor: move render-phase sync strategy into core reactivity bindings

Builds on the deferred controlled-state publication from this branch and
consolidates it behind a consistent adapter interface:

- TableReactivityBindings gains two optional properties describing the two
  strategy axes: deferExternalStateSync (write-side: is setOptions a
  notification-safe moment?) and commit (invalidation hook for readonly atoms
  whose compute reads non-reactive plain options). constructTable warns in dev
  when defer is set with plain options but no commit hook.
- table_setOptions consults the bindings flag instead of a per-call
  { syncExternalState } option, so an adapter's strategy is declared once.
- table_syncExternalStateToBaseAtoms replaces the arguments.length overloads
  with an explicit `capturedState | null` sentinel, and now owns the commit
  bump: it runs inside the write batch and fires even when nothing is
  published, so ownership releases still invalidate subscribers.
- New renderPhaseReactivity preset in @tanstack/table-core/reactivity hosts
  the live readonly-atom facade + commit atom (moved from the React adapter).
  Store primitives are injected by the adapter so all atoms share one store
  instance with user external atoms. Preact can adopt the same preset later.
- New createCommitFilteredSource replaces useTableSelector: because facade
  snapshots are referentially stable, a reference check on the last snapshot
  read is enough to skip the root hook's redundant post-commit notification.
  This drops the committed-selection refs and the implicit requirement that
  the selector's layout effect run before the publish effect.
- useTable: plain useSelector over the filtered source; the publish layout
  effect is a single table_syncExternalStateToBaseAtoms call.

All 11 react-table tests from this branch pass unchanged. table-core: 1017
tests, types, lint, size-limit green. Both example e2e smoke suites pass.
Verified in basic-external-state (StrictMode + React Compiler + devtools):
one render pass and one commit per controlled update, no render-phase
warning, correct behavior through pagination/sorting/page-size/1M-row stress.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix: adopt render-phase reactivity preset in the preact adapter

Preact had the identical sync-options-during-render code as React and paid
the same cost silently: the mid-render store notification scheduled an extra
deferred render per controlled update (Preact never warns about it).

Same shape as the React adapter: preactReactivity collapses onto
renderPhaseReactivity with @tanstack/preact-store primitives, useTable defers
publication to an isomorphic layout effect with the captured controlled
state, and the root useSelector reads through createCommitFilteredSource.

New unit tests assert one render pass per controlled update with consistent
controlled/selected/atom/store/row-model reads, exactly one post-commit store
notification for external subscribers, and uncontrolled updates still
re-rendering. New e2e spec exercises controlled pagination in the
basic-external-state preact example. Types, lint, and build green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix: adopt render-phase reactivity in the lit adapter, un-pin subscribe islands from stale renders

The lit basic-subscribe e2e regression had two stacked causes:

1. The subscribe directive returned noChange for host-driven re-renders with
   an unchanged source + selector, so islands only ever updated from store
   notifications. They previously received one for ANY setOptions call
   because the aggregate state snapshot was rebuilt without a comparator;
   the (correct) shallow compare on table.store stopped notifying for
   options-only changes, pinning islands to stale row models after
   Regenerate Data. The directive now re-renders islands on every host
   update and adopts the latest template closure, while subscriptions still
   drive updates between host renders.

2. Lit was the off-diagonal reactivity case: a reactive options store
   written during render(), costing a second update cycle per interaction
   (requestUpdate mid-update from the optionsStore subscription).
   litReactivity now uses the renderPhaseReactivity preset with
   @tanstack/lit-store primitives: plain options synced during render,
   captured controlled state published from hostUpdated(), and the
   controller's root subscription reads through createCommitFilteredSource.
   The optionsStore subscription is gone; options changes flow through host
   renders (lit reactive properties), which 30 of 31 lit examples already
   use. basic-subscribe was the lone outlier constructing the table once
   and pushing data via imperative setOptions in updated() — it now
   re-syncs options per render pass like the rest.

Measured on basic-subscribe: Regenerate Data works again with one host
update (previously two, with stale islands), zero idle update churn, and a
row-selection click still updates only its island with zero host updates.

Unit tests: directive/controller suites updated to the new contract plus a
hostUpdated publication test (6/6). All 34 lit example e2e suites pass,
including the previously failing basic-subscribe. Types, lint, build green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* test: drop dev-warning assertion to match removed bindings coherence warning

The constructTable dev warning for deferExternalStateSync-without-commit was
removed in the previous commit; align the test suite (1010 tests green).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci: apply automated fixes

* consolidate constructTable features loop again

* fix: keep the two-phase feature lifecycle in the consolidated features loop

The consolidated loop interleaved constructTableAPIs with
initTableInstanceData per feature (and ran APIs first within each feature),
breaking the lifecycle contract from #6446 that constructTable.test.ts
encodes: every feature's table instance data initializes before ANY table
APIs are constructed, so API constructors can read instance data owned by
other features and init hooks observe a pre-API table.

Keep the consolidation of the init-fn collection with instance-data init
(one phase-1 loop writing the precomputed arrays directly), and restore
constructTableAPIs as its own second pass.

table-core: 1097/1097. React/preact/lit adapter suites green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* refactor!: process feature lifecycle hooks in a single pass

Drop the two-phase construction contract (all initTableInstanceData before
any constructTableAPIs). Every in-repo hook is pure property assignment with
lazy API closures, so the phase barrier bought nothing; features are now
processed in one registration-order pass with each feature's instance data
initialized just before its own APIs are constructed.

New contract, encoded in the lifecycle test and documented in the
custom-features guides and TableFeature jsdoc: hooks may rely on data and
APIs of features registered earlier; eager cross-feature reads belong in
lazy API bodies.

table-core 1097/1097; react/preact/lit adapter suites green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* refactor: require precomputed instance-init fn arrays on the table type

constructTable always assigns the five _*InstanceInitFns arrays before any
constructor can run, so model them as required and drop the non-null
assertions at the use sites (including the leftover one in buildHeaderGroups
that eslint flagged as unnecessary).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

* clean up

* fix some issues exposed by MRT examples

* add more react smoke tests

---------

Co-authored-by: Kevin Van Cott <kevinvandy656@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-29 16:59:21 -05:00
Kevin Van Cott
6415183c9f
feat: cell selection feature (#6455)
* feat: cell selection feature

* pr feedback and fix svelte loop

* fix test
2026-07-25 20:45:15 -05:00
James Garbutt
441cf7449f
perf(table-core): pre-compute instance init functions (#6446)
* perf: pre-compute instance init functions

When we construct a row, we iterate over the table's features and
initialise any which have an `initRowInstanceData`.

This is expensive since most don't have such a method.

We actually know when we construct the table which features have this
method. This changes the table construction to store the initialisers up
front so when we create a row, we can just iterate the already known
initialisers.

* fix(table-core): bind initialiser to feature

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* cache init functions consistently for all table objects

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: Kevin Van Cott <kevinvandy656@gmail.com>
2026-07-24 11:15:58 -05:00
Kevin Van Cott
209699ff77
docs: rewrite faceting guides and bucketd faced example 2026-07-17 18:26:00 -05:00
Kevin Van Cott
6acc1e9215
fix: rename to rowAggregationFeature and rewrite migration guides (#6423)
* fix: rename to rowAggregationFeature and rewrite migration guides

* ci: apply automated fixes

* update feature name in migration guide

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-15 21:45:07 -05:00
Kevin Van Cott
66f7508801
fix: add back sub-rows onto aggregate context (#6421)
* fix: add back sub-rows onto aggregate context

* aggregate from sub-rows by default first like v8 behavior

* new APIs for custom aggregation depths

* fix example signatures

* update docs
2026-07-15 18:46:56 -05:00
Kevin Van Cott
f265513e01
feat: aggregation overhaul as a standalone feature (#6418)
* feat: aggregation overhaul as a standalone feature

* finish updating rest of examples and guides
2026-07-14 12:48:08 -05:00
Kevin Van Cott
eba5386a67
feat: new filter, sort, aggregation Fns, and recommended import patterns (#6415)
* feat: new filter, sort, aggregation Fns, and recommended import patterns

* fix some examples
2026-07-12 20:47:49 -05:00
Kevin Van Cott
e90cfdcfd4
feat: batch row selection (#6409)
* feat: batch row selection

* fix tests

* pr feedback and add migration guide note

* no more e2e in pr

* fix angular examples double building in ci tests

* fix type
2026-07-12 11:04:00 -05:00
Kevin Van Cott
234a9db671
feat: regenerate skills (#6404)
* feat: regenerate skills

* fix node version in check skills

* fix check skills pipeline

* fix workspacePaths
2026-07-10 20:21:40 -05:00
Kevin Van Cott
e91608ea2f
feat: update column pinning terminology from left/right to start/end (#6398)
* feat: update column pinning terminology from left/right to start/end

* update beta number

* update variable names and clarify left to right associations
2026-07-10 08:01:09 -05:00
Kevin Van Cott
0e56a4da22
docs: rewrite migrating guides (#6378) 2026-07-03 22:46:43 -05:00
Kevin Van Cott
c1c959e0f0
docs: update column resizing advanced performance sections 2026-07-02 18:39:05 -05:00
Kevin Van Cott
c11ad756b6
fix: useTableContext hmr and type fixes (#6355)
* fix: useTableContext hmr and type fixes

* tselected

* regen docs
2026-06-28 17:43:30 -05:00
Kevin Van Cott
f077ae73c3
fix: improve row selection api performance (#6344) 2026-06-24 23:06:57 -05:00
Kevin Van Cott
a471632a3c docs: improve composable table guides 2026-06-24 12:21:07 -05:00
Kevin Van Cott
17b84c3646 docs: update feature setup sections 2026-06-24 07:36:45 -05:00
Kevin Van Cott
a84475b17b
feat: refactor features option to include row models and fns (#6318)
* feat: refactor features option to include row models and fns

* ci: apply automated fixes

* fix column/global filtering feature relationship in types

* fix TData in custom filterFns

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-06-12 09:38:52 -05:00
Kevin Van Cott
4108c59bfd
feat: per table, table meta and column meta (#6316) 2026-06-11 09:38:34 -05:00
Kevin Van Cott
e25a532ae8 docs: beta docs pass 2026-06-10 20:45:40 -05:00
Kevin Van Cott
ab4208b94f docs: add more migration guides 2026-06-09 12:51:30 -05:00
Kevin Van Cott
29bea700a0 docs: re-organize feature guides to be framework specific 2026-06-09 10:18:53 -05:00
Kevin Van Cott
be6a9323c0 docs: regen api ref and refactor composable tables guides 2026-06-09 07:51:38 -05:00
Riccardo Perra
8412d5d2a2
feat: enable support for native reactivity in solid vue adapters (#6298)
* chore: update examples to use table.store.get() instead of removed table.state

* feat: refactor solid/vue native reactivity adapter

* ci: apply automated fixes

* ci: apply automated fixes (attempt 2/3)

* fix: update all examples to call table.atoms instead of table.store

* ci: apply automated fixes

* fix(vue): call reactivity unmount on scope dispose

* correct merge conflict resolution and regen lock file

* fix sherif issue

* update table state docs

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Kevin Van Cott <kevinvandy656@gmail.com>
2026-06-07 12:14:47 -05:00
Kevin Van Cott
60e4d7b371
feat: drop the underscore. It's cleaner (#6296)
* feat: drop the underscore. It's cleaner

* simplify
2026-06-05 13:39:35 -05:00
Riccardo Perra
63ea77ce67
feat: add angular devtools support and fix core devtools reactivity (#6248)
* feat: add angular devtools

* fix(table-devtools): fix table state reactivity

Refactor devtools panel with a more solid-idiomatic approach, using memo and dynamic `useTableState` subscription via Accessor getter to not break reactivity.

* Add devtools in all angular examples

* Use a stable identifier reference to register devtools in table

* Fix dependency versions

* ci: apply automated fixes

* generate instanceId for react-table

* fix basic external store examples
mark table.store as deprecated in adapter table types
replace table.store.state with table.state in examples

* add external atoms example in angular

* update package lock

* ci: apply automated fixes

* update angular adapter for readonly atom reactivity pattern

* add missing angular examples (WIP)

* clean up devtools on examples

* fix some angular reactivity

* ci: apply automated fixes

* fix solid and svelte reactivity issues

* update docs gen

* apply pr feedback

* make state reads consistent in angular examples

* ci: apply automated fixes

* fix infinite render in angular column-pinning-split

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Kevin Van Cott <kevinvandy656@gmail.com>
2026-05-29 10:49:41 -04:00
Kevin Van Cott
1b3deca86b
regen static function jsdoc (#6270) 2026-05-16 21:41:59 -05:00
Kevin Van Cott
db0c2d9b5a
fix: simplify some column pinning + visibility memo deps and performance (#6259)
* fix: simplify some column pinning + visibility memo deps and performance

* fix pnpm link issue with match-sorter-utils
2026-05-13 14:21:54 -05:00
riccardoperra
576ae62546 feat(angular): remove angular value state selector
- Align docs with new api
2026-05-11 20:29:02 +02:00
Kevin Van Cott
90a825b84b docs: update getting started and api ref doc links 2026-05-10 14:43:09 -05:00
Kevin Van Cott
3ac7146a66 docs: rewrite table-state guides for v9 2026-05-10 11:31:03 -05:00
Kevin Van Cott
c5c781aa99
feat: change default state selectors to all (#6246)
* feat: change default state selectors to all

* add basic-subscribe example
2026-05-08 12:37:06 -05:00