taTanStack
GitHubtableWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionCanceled
      fix/inNumberRange-autoRemove-non-array-value
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runCanceled
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    fix(table-core): guard Array.isArray before index access in range autoRemove fns filterFn_between, filterFn_betweenInclusive, and filterFn_inNumberRange all had: autoRemove: (val: any) => testFalsy(val) || (testFalsy(val[0]) && testFalsy(val[1])) When a scalar (non-array) value like `99` is passed, `val[0]` and `val[1]` are both `undefined`. testFalsy(undefined) === true, so the second branch evaluates to `(true && true)` === true and the filter is immediately removed — even though 99 is a perfectly valid, non-empty filter value. Root-cause: numeric columns default to the `inNumberRange` filter function (auto-selected in column_getAutoFilterFn). Calling `col.setColumnFilter(99)` hits this path and the filter silently vanishes (issue #5949). Fix: add `Array.isArray(val) &&` so the index checks only run when val is actually an array. The testFalsy(val) head still removes undefined/null/''. Closes #5949
    nx affected --targets=test:eslint,test:sherif,test:knip,test:lib,test:types,test:build,build --parallel=3
Canceled
6353
<1%

Completed tasks

2 of 453 completed.

99%

Not executed tasks

451 of 453 tasks were not executed.

<1%

Cache hits

2 of 453 tasks used cache.

Atomizer enabled

2 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubtableWorkspace