CodeVetter · Repo Unpack · Data flow
TanStack/table
Applications supply row data, column definitions, feature configuration, and optional external state owners. Construction turns configuration into effective state atoms and feature APIs; row-model reads then derive renderer-facing rows. Updates pass through owner-specific callbacks rather than a durable storage layer in the inspected core. Additional boundaries include worker message transfer, example query caches, and example-owned browser persistence.
- createCoreRowModel memoizes on options.data identity. accessRows assigns IDs through getRowId, constructs rows, populates flatRows and rowsById, and recursively reads children through the optional getSubRows callback.
- constructTable removes metadata slots, row-model factories, and function registries from actual feature modules, combines remaining modules with coreFeatures, and invokes their defaults and initialization hooks.
- Effective state reads prefer options.atoms[key], then an own property in options.state, then baseAtoms[key]. Explicitly undefined controlled slices fall back to initialState, and table.store aggregates effective slice values.
- table_setSorting calls setStateSlice, which resolves onSortingChange and evaluates its equality guard inside the owner's updater. The default makeStateUpdater writes to an external atom when supplied, otherwise to the internal base atom.
- React stages current options during render without synchronizing external state, selects a shallow-compared root snapshot, then marks that render committed and publishes its captured controlled state in an isomorphic layout effect.
- Worker synchronization sends changed data separately from requested stages and state. The shadow table batches received state into base atoms, computes requested models, serializes payloads with transferables, and returns requestId/dataVersion for acceptance checks.
- The Query example places pagination, sorting, and globalFilter in its query key, calls local fetchData, and passes returned rows/rowCount into a manually processed table. fetchData waits 500 ms, filters/sorts generated data, and slices the requested page.
- The shadcn-base example owns theme persistence: ThemeProvider reads vite-ui-theme from localStorage, validates light/dark/system, writes selections back, and applies the effective theme as a document-root class.