MinWidth config

[philcunliffe]

Adds an optional minWidth to the column configuration

[severo]

Overall, I wonder: maybe we could create a context for the columns configuration, and its provider would be the outermost:

function HighTableData(props: PropsData) {
  const { data, key, version } = useData()
  const { numRows } = data
  // TODO(SL): onError could be in a context, as we might want to use it everywhere
  const { cacheKey, orderBy, onOrderByChange, selection, onSelectionChange, onError } = props

  return (
    <ColumnConfigurationProvider value={props.columnConfiguration}>
      /* Create a new set of widths if the data has changed, but keep it if only the number of rows changed */
      <ColumnStatesProvider key={cacheKey ?? key} localStorageKey={cacheKey ? `${cacheKey}${columnStatesSuffix}` : undefined} numColumns={data.header.length} minWidth={minWidth}>
        {/* Create a new context if the dataframe changes, to flush the cache (ranks and indexes) */}
        <OrderByProvider key={key} orderBy={orderBy} onOrderByChange={onOrderByChange} disabled={!data.sortable}>
          {/* Create a new selection context if the dataframe has changed */}
          <SelectionProvider key={key} selection={selection} onSelectionChange={onSelectionChange} data={data} onError={onError}>
            {/* Create a new navigation context if the dataframe has changed, because the focused cell might not exist anymore */}
            <CellsNavigationProvider key={key} colCount={data.header.length + 1} rowCount={numRows + 1} rowPadding={props.padding ?? defaultPadding}>
              <PortalContainerProvider>
                <HighTableInner version={version} {...props} />
              </PortalContainerProvider>
            </CellsNavigationProvider>
          </SelectionProvider>
        </OrderByProvider>
      </ColumnStatesProvider>
    </ColumnConfigurationProvider>
  )
}

and use that configuration inside the ColumnStates context, so that the rest of the code would not have to touch the minWidth parameter.

Alternatively, consume columnConfiguration as a prop of ColumnStatesProvider directly, which expands the scope of the context, but would be simpler, I guess

---

Otherwise, only some comments.