fix numeric zero global filters#6432
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughGlobal filtering and faceting now distinguish inactive values from falsy values, allowing ChangesGlobal filter activation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
View your CI Pipeline Execution ↗ for commit 9a8fa98
☁️ Nx Cloud last updated this comment at |
What changed
0as an active global filter valueundefined,null, and the empty stringWhy
The row-model pipeline used truthiness to decide whether global filtering was active. That skipped
0, even though numeric status values are valid filter inputs.The filtered model and faceted model now agree on explicit empty values instead of relying on truthiness.
Validation
packages/table-core/tests/implementation/features/column-filtering/createFilteredRowModel.test.ts— 27 tests passedgit diff --checkCloses #4488
Summary by CodeRabbit
Bug Fixes
0now work correctly.Tests
0.