-
Notifications
You must be signed in to change notification settings - Fork 932
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(#1747): Replace deprecated props in mui based components #1748
fix(#1747): Replace deprecated props in mui based components #1748
Conversation
- Used TransitionProps instead of the deprecated onClose and onExited Props for material-ui based Popover. - Used onPageChange and onRowsPageChange Props instead of the deprecated onChangePage and onChangeRowsPerPage Props respectively, for material-ui based TablePagination. - Used ref instead of the deprecated buttonRef for material-ui based IconButton .
There is any estimate to implement this PR? |
+1 |
Please can this be merged, thank you... |
When it's going to be released? |
If anyone is facing this problem on production and needs to fix this immediately, I've created a fork from this repo and merged this PR on own master and created a manual release Run this on your terminal: yarn add https://github.com/penseapp/mui-datatables or npm i https://github.com/penseapp/mui-datatables WarningThis will work but needs to be temporary, after merge of this PR, you should alter your package.json again! |
I haven't seen any response from those with the power to push changes, I've had luck with @wdh2100 reviewing and pushing changes. Maybe we can summon him. |
I can't install the fork and get error messages beginning with "npm ERR! prepareGitDep |
Hoping for this to get merged soon, saves us forking the repo temporarily |
@gregnb when you can merge this PR? There are others maintainers on this repo also to help you out? |
please is there a fix already? v3.7.8 still throws the same errors |
Its waiting on a merge. 3.7.8 wouldn't contain the fix. |
up ? |
@gregnb we're waiting for some feedback, can you please increase the maintainers on this repository? |
I do home covid didn't get you @gregnb :( |
Now you're saying that I got quite worried. It's been a while since his last activity in Github. |
Any movement on this? |
Please any update? |
@gregnb you good? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Kalaiz LGTM 👍
Forgive me for being late. 😢
I was just about to make a manual fork, you couldn't have had better timing! Thanks! |
It will be released(3.8.0) soon with some bugs. |
@wdh2100 Some bugs I can work with! Do you have a rough estimate for when it will be released? |
Release 3.8.0 |
issue still ongoing...resorted to using: |
Material-ui will be migrating from v4 to v5 and has been deprecating stuffs as a part of that move. Deprecation warnings as stated in #1747 appears when MUI-Datatable is used. This PR fixes it by using the recommendations provided by material-ui, in regards to the deprecations.
Used
TransitionProps
instead of the deprecatedonClose
andonExited
Props for material-ui based Popover.Used
onPageChange
andonRowsPageChange
Props instead of the deprecatedonChangePage
andonChangeRowsPerPage
Props respectively, for material-ui based TablePagination.Used
ref
instead of the deprecatedbuttonRef
for material-ui based IconButton. Note: In addition to those mentioned in Warnings from deprecated\old props #1747, I faced the below warning as well:If I am not wrong, I believe it is caused by the warnings added in material ui 4.12.0 release and there are indeed going to remove
buttonRef
as seen in one of the v5 pre-releases.I tried running the
npm test
, however, I faced the same error as mentioned in here.