Column width calculated wrong

[dmitri256]

Currently column width is max from title width and average with of data in column. It is wrong, because if column has some empty rows and other are comparable long, then contents of not empty rows are cutten. To fix this it is necessary to take max length of data in column instead of average.

[pavankataria]

Can you submit a PR with test cases, and screenshots of before and after?

[pavankataria]

Sorry for the delay. So in 0.8.2 widths are based on average character counts as you correctly said, so long values will clip due to average width calculations.

In the upcoming release I added a column width strategy API. If you want “no clipping” you can either:

• Use columnWidthStrategy = .maxMeasured (measures every cell; widest wins), or
• Keep widths capped and enable textLayout = .wrap + rowHeightMode = .automatic for multi‑line rows.

Example:

var config = DataTableConfiguration()
config.columnWidthStrategy = .maxMeasured
config.maxColumnWidth = nil // allow width growth

// OR

config.textLayout = .wrap
config.rowHeightMode = .automatic(estimated: 60, precompute: true)

You can also do per‑column strategies via the upcoming columnWidthStrategyProvider.
There's also finally autolayout capabilities allowing you to use custom self-sizing cells - where you can place a label with constraints defined and the label numberOfLines set to 0 for multiline support with dynamic heights!

[pavankataria]

Hey, I've fixed this in v0.9.0. Column width calculation has been completely rewritten with O(n) sampling strategies instead of the previous O(n²) approach.
Please see the Column Widths documentation for available strategies.