Repository navigation
Conversation
`Column.frozen` now only accepts `ColumnFrozen` (`false | 'start' | 'end'`). `true` was kept as an alias for `'start'` for backward compatibility with 6.x; it is now a type error and is no longer normalized. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4260 +/- ##
=======================================
Coverage 99.27% 99.27%
=======================================
Files 44 44
Lines 2204 2204
Branches 965 965
=======================================
Hits 2188 2188
Misses 16 16
🚀 New features to boost your workflow:
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Most columns are not frozen, so they now take one comparison instead of two. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Unfrozen columns are the most common, then start-frozen ones, so `getColSpan` and the column sort now compare `frozen` with `false` first, then with `'start'`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Column.frozennow only acceptsfalse,'start', or'end'. When'start'and'end'arrived in beta.60 (#4034),truestayed on as an alias for'start'so that 6.x code kept working. 7.0.0 drops the alias. Without it, the type is justMaybe<ColumnFrozen>, and the grid no longer has to converttrueto'start'.Breaking change
Column.frozenisfalse | 'start' | 'end'.true, which was accepted as an alias for'start', is now a type error.Changes
Column.frozenis typedMaybe<ColumnFrozen>, and its JSDoc no longer mentions the alias.useCalculatedColumnsnow usesrawColumn.frozen ?? falseinstead of convertingtrue.getColSpanand the column sort inuseCalculatedColumnscomparefrozenwithfalsefirst, then with'start', since unfrozen columns are the most common, then start-frozen ones.SelectColumnand the group-by columns ofTreeDataGridusefrozen: 'start'.frozenentry drops the backward-compatibility wording, and theColumnFrozen"See also" link points to the renamed anchor (#frozen-maybecolumnfrozen).frozen: trueis treated as'start'. The other tests now use'start'.frozen: i < 5used to type-check because they evaluate totrue | false. They are type errors now, so the website demos (ColumnSpanning,MillionCells,ScrollToCell,VariableRowHeight) and tests (colSpan,startFrozen,keyboardNavigation,scrollToCell) usei < 5 ? 'start' : false. Apps that computefrozenfrom a boolean need the same change.Verification
vp run cipasses. I also built the package withvp packand type-checked a scratch consumer againstlib/index.d.tswithtsc --strict, both with and without--exactOptionalPropertyTypes:'start','end',false,null, andundefinedare accepted, andtrueis a type error.🤖 Generated with Claude Code