-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
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
[lab] Update @mui/x-date-pickers
to have the lab usable with React 18
#32828
Conversation
c622cda
to
37d60aa
Compare
@material-ui/core: parsed: +Infinity% , gzip: +Infinity% |
@@ -46,8 +46,8 @@ | |||
"@mui/x-data-grid": "^5.8.0", | |||
"@mui/x-data-grid-generator": "^5.8.0", | |||
"@mui/x-data-grid-pro": "^5.8.0", | |||
"@mui/x-date-pickers": "^5.0.0-alpha.0", | |||
"@mui/x-date-pickers-pro": "^5.0.0-alpha.0", | |||
"@mui/x-date-pickers": "^5.0.0-alpha.3", |
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.
I updated the version on the doc to have less bugs on the examples (https://mui.com/x/)
I have updated the issue description to mention two other issues I think this PR fixes. |
I have renamed this PR title. I think that we solve a problem for developers who want to use components in the |
@mui/x-date-pickers
to have the lab usable with React 18
version "5.0.0-alpha.0" | ||
resolved "https://registry.yarnpkg.com/@mui/x-date-pickers/-/x-date-pickers-5.0.0-alpha.0.tgz#a62ffbab453d3c2dcd4ec20bd4f3f6338ad2ed3f" | ||
integrity sha512-JTzTaNSWbxNi8KDUJjHCH6im0YlIEv88gPoKhGm7s6xCGT1q6FtMp/oQ40nhfwrJ73nkM5G1JXRIzI/yfsHXQQ== | ||
"@mui/x-date-pickers@5.0.0-alpha.1": |
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.
Was this intentional instead of alpha.3
?
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.
Yes
The goal here is just to avoid blocking users that uses the lab for others components than the pickers and who want React 18
But for the pickers, you should migrate to the new packages. Those components will soon leave the lab
Fixes mui/mui-x#4932
Fix #32319
Fix #32654