Mui-datatables: Is there a plan of migration to material-ui v5?

[yaminyaylo]

The issue is when I updated the Material-UI library to the latest version I found out that MUI-datatables doesn't support the Material-UI library v5.

Updated Material-UI libs to the following versions:

• "@material-ui/core": "5.0.0-alpha.9",
• "@material-ui/icons": "5.0.0-alpha.7",
• "@material-ui/lab": "5.0.0-alpha.9",
• "@material-ui/pickers": "^4.0.0-alpha.12",
• "@material-ui/styles": "5.0.0-alpha.8",

Expected Behavior

No errors and crashed on the Table filter action.

Current Behavior

There are errors and crashed on the Table filter action press.

I guess this issue is due to Material-UI library new version - The onE* transition props were removed. Use TransitionProps instead. https://github.com/mui-org/material-ui/releases/tag/v5.0.0-alpha.7

Steps to Reproduce (for bugs)

1. update material-ui and it's dependant libs to the latest
2. fix all breaking changes in your app
3. go to the page you have a table based on MUI-datatables
4. suppose it has passed data inside the table and filter option is true
5. click on the Filter icon button
   

Your Environment

| Tech | Version |
|--------------|---------|
| Material-UI | 5.0.0-alpha.9 |
| MUI-datatables | 3.4.1 |
| React | 16.13.1 |
| browser | Chrome (latest) |
| etc | |

[patorjk]

I would accept pull requests to get the table working on version 5. If it requires breaking changes, it'd require a version bump and would probably be worth waiting until the official version 5 is released. I have not yet used version 5.

Also worth mentioning: The Material UI team is actually going to release an official data-table component for version 5.0. I talked with the lead Material UI dev a few months ago about it, and chatted back and forth through email around 6-7 weeks ago with the developer they have working on the official data-table (I tried the table out and then made a bunch of suggestions - the table looks pretty good and the developer seemed very receptive to my feedback). The goal is to get rid of the need for 3rd party data-tables like mui-datatables and material-table. However, the unfortunate thing is that many of the features that mui-datatables currently supports will be locked behind a paid enterprise version (at least that was the case 6-7 weeks ago), so I'm assuming there will still a place for mui-datatables and material-table, but I've sort of taken a wait-and-see approach by not doing too much development, as I'm not sure what direction the community will go. However, I'm open to PRs from other devs.

[yaminyaylo]

@patorjk thanks a lot for a very quick response and explanation.

I will think about what to do next.