Tables column names overriden

[jeremiedb]

Not a bug per se as it seems a deisgn choice, but the introduction of the override of column names in DataTableOptions in v0.22.9:

StippleUI.jl/src/Tables.jl

Line 158 in 584f88f

[Column(string(name), sortable = true, label = label_clean(name)) for name in TablesInterface.columnnames(t.data)]

happened to be undesirable for our applications. I would personally favor in general limited stylistic side effects from functions by default. Could adding a kw arg in DataTableOptions for specifying custom column names as Vector{String} cover those custom names needs, or having an opt-in "clean_colnames" boolean indicator?

[hhaensel]

I agree that uppercasing is a bit surprising, maybe we re-think/revise this or offer a kwarg to replace label_clean by a customer function, e.g. x -> string(x) or identify.

Meanwhile there's an easy solution to this that you can implement yourself, assuming that you are using DataFrames

mycolumns(df) = [Column(string(name), sortable = true, label = string(name)) for name in names(df)]
puredatatable(df) = DataTable(df, DataTableOptions(columns = mycolumns(df)))

dt = puredatatable(df)