CodeVetter · Repo Unpack · Contributor handoff
TanStack/table
Begin with contribution rules, then follow the affected feature from example controls into core utilities and adapter publication. Core changes have cross-framework reach, so distinguish algorithm behavior from framework scheduling and rendering contracts. Tests and CI were inspected, not executed in this audit; future execution requires a separately authorized environment. The inventory and investigation are bounded, and source comments or configured checks must not be reported as runtime verification.
- Read CONTRIBUTING.md before analysis or changes, keep a PR focused on one topic, understand AI-generated changes, preserve the required PR sections, and add a changeset for published-package changes.
- Use the root pnpm workspace and existing Nx scripts. build targets affected packages; build:all targets all non-example packages; package-level test:lib, test:types, and test:build provide narrower starting points for authorized verification.
- For code contributions, CONTRIBUTING.md requires both pnpm test and pnpm test:e2e before opening a PR, with browser installation potentially needed. This audit inspected those commands and CI definitions without executing them.
- Preserve documented dependency exceptions: TypeScript 6.0.3, Ember Babel 7.29.7, Svelte dnd-kit 0.2.x, Vitest 4, Octane 0.1.36, specified Pacer devtools versions, and Preact Form 1.30.5 require separate migrations.
- Before changing state ownership, read constructTable, coreTablesFeature.utils, and setStateSlice. External atoms outrank controlled state, equality runs against the owner's value, and option merging preserves initial features, atoms, and initialState.
- For React changes, preserve render-versus-commit publication and stable App wrapper component identities. useAppTable keeps current tables in a ref because useTable returns a changing object; recreating wrappers would remount subtrees and disrupt focused inputs.
- For worker changes, inspect both bridge and shadow-table code plus shared example configuration. Preserve dataVersion/request checks, coalescing, consistent processing functions, pre-result fallbacks, and explicit termination semantics.
- Keep scope-specific verification distinct: adapter tests target lifecycle/state integration, worker unit tests use a fake transport, Playwright targets Chrome, and coverage has no thresholds. None of these inspected definitions establishes full adapter/browser coverage or a passing result.