Overview - Table

tableWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

table

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

tableWorkspace

Canceled
6353
6a8e0461 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
by JSap0914