taTanStack
GitHubtableWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      fix/column-resize-clamp-min-max-size
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    fix(table-core): clamp column size to minSize/maxSize during resize drag The getResizeHandler drag loop computed new column widths without ever checking the column definition's minSize or maxSize constraints. Dragging a resize handle far left or right could push a column outside the bounds declared in columnDef, making the constraints ineffective at runtime even though column_getSize (used for committed state reads) does apply the clamp. Fix by capturing each leaf column's minSize/maxSize at drag-start time into a closure map (columnSizingConstraints), then applying Math.min(maxSize, Math.max(minSize, rawSize)) before writing into newColumnSizing. Two new tests confirm the bounds are respected for both directions.
    nx run-many --targets=build --exclude=examples/**
Succeeded
Linux
4 CPU cores
ad3436e76295
7%

Cache hits

1 of 15 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

15 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubtableWorkspace