fix(table-core): skip onColumnVisibilityChange for a redundant toggle-all - #6540
Open
lazerg wants to merge 1 commit into
Open
fix(table-core): skip onColumnVisibilityChange for a redundant toggle-all#6540lazerg wants to merge 1 commit into
lazerg wants to merge 1 commit into
Conversation
lazerg
force-pushed
the
fix/issue-6539-toggle-all-columns-visible-noop
branch
from
August 11, 2026 00:41
9323898 to
45e481d
Compare
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
📝 WalkthroughWalkthrough
ChangesColumn visibility no-op
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 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 |
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Changes
table_toggleAllColumnsVisiblerebuilds the whole visibility map and hands it totable_setColumnVisibilityunconditionally, so asking for a state the table is already in still runsonColumnVisibilityChange:setStateSlicecan't catch this one. The map it receives ({ id: true, firstName: true, ... }) is structurally different from the{}the state usually holds while every column is visible, so the two never compare equal. The fix compares the map against each leaf column's current visibility instead and returns early when they already agree, the same kind of explicit no-op checktable_toggleAllRowsExpandedkeeps.Two existing tests toggled all columns on from a table where everything was already visible, which is now a no-op. Both start from a hidden
firstNameinstead, so they still exercise the show-all path.Fixes #6539
✅ Checklist
pnpm run test:pr.Two tests added to
columnVisibilityFeature.utils.test.ts, both verified to fail onmain: one for the already-all-visible case, one for the already-all-hidden case.🚀 Release Impact
Summary by CodeRabbit
Bug Fixes
Documentation