mui-datatables v3.2.0

[patorjk]

Branch for the 3.2.0 release of mui-datatables. It contains the following:

• Added setFilterChipProps option - An option to set props on the filter chips (Added setFilterChipProps #1387)
• Refactored out unsafe_componentWillMount - Should now allow the table to run in strict mode without warnings (Refactored out unsafe_componentWillMount #1388, React.StrictMode prevent removing filter #1261)
• Added currentTableData to tableMeta parameter of customBodyRender. This field is an array of objects, where each object points to a row of data in the table and provides the dataIndex to the external data. This resolves consistency problems with tableMeta.tableData. If there is a version 4 of mui-datatables, tableMeta.tableData will be removed. (Can calling with updateValue() in customBodyRender() cause other columns to update? #1405, Force consistency with table metadata between array and object data #933)
• Added jumpToPage option - This option, if true, adds a "Jump to Page" dropdown to the table footer that allows users to navigate to a specific page. (Added jumpToPage option #1398)
• Added TableViewCol and Checkbox to components property. This allows custom versions to be inputted. For example, using a checkbox with a different color. The large-data-set example has been updated to show custom versions of these components in action. (Added TableViewCol and Checkbox to components property (so that custom versions can be inputted) #1399, Unable to show/hide columns with CustomRowRender #1250 (comment), Customize color of the select row checkboxes at the side of the table #1255, Rather than checkbox is there a way to make star? #1249)
• Added customHeadLabelRender column option. This creates a custom render function for the table's header cell label. The label's display in other areas (such as the View Columns popover), will still use the column's label. (Enhancement/custom head render as child #955 (comment))
• Fix to allow using a component in textLabels.body.noMatch without getting a warning. (Allow specifying component for Typography in case of no matches #1403, Localization textLabels values as React components #1401)
• Deprecation typo fix. (Incorrect V3 deprecation message for onRowsExpand #1402)
• Fixed issue with dragging columns that have nested mui-datatables in their expanded rows. (Side effects when dragging columns with nested MUIDataTables #1406)
• Fixed issue with setCellProps. (setCellProps changed following V3 update #1414)
• Fixed issue with customFilterListOptions.update. (customFilterListOptions.update is broken #1407)
• Replaced classnames package with clsx. This is the package Material UI uses. It has the same API as classnames but is faster and smaller. Thanks to @cahna (Replace classnames with clsx #1409).
• Example updates with clsx. Thanks to @wdh2100 (Replace classnames with clsx in example #1415)
• Several components refactored into hooks. Thanks to @wdh2100 (Refactoring TableSearch and TableViewCol #1351, Refactoring TableFooter #1349, Refactoring TablePagination #1347)

A beta version is available via:

npm install mui-datatables@v3.2.0-beta.2

Currently a work in progress, will probably be released next week.

[coveralls]

Coverage increased (+1.3%) to 72.375% when pulling 9c2d14d on v3_2_0 into efd5f1e on master.

[cahna]

Would you accept a PR to replace classnames with clsx? Only suggesting because I learned today that @material-ui/core uses clsx.

[patorjk]

Just finished looking into it (mui/material-ui#14152). Smaller, faster, same API, and Material UI switched from classnames to clsx. I'd would accept a PR for this change.