-
Notifications
You must be signed in to change notification settings - Fork 325
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
Migrate Material UI version to v5 #1694
Comments
Hi @phixMe, I looked into picking this one up. Tried to upgrade to React 17 and ran into a couple problems:
I'm not sure what to do about either of the above problems. Maybe they need to be separate issues that we should discuss and fix first? Side note: I'm not sure what other problems we may face upgrading to v17, since at the moment I can't get past the |
Hi @dakshin-k, thanks for looking into this. I think we can actually drop I think we should look into migrating to I can create issues for both of these. |
@dakshin-k I've fixed both of the issues you've reported in the following PR. #2197 |
Perfect! I'll try to raise a PR upgrading to React 17 over the next few days |
Found another problem, and a biggie - Enzyme doesn't support React 17 There is an unofficial fork that seems quite popular, however the author has said there won't be a version for React 18. For now, we might be able to switch to this fork for tests (Let me know if I can raise a PR to do that). |
I think we should just move over to |
The main UI package we use across our project has made some major changes with the new major release and has a long list of migration actions.
https://mui.com/guides/migration-v4/#update-react-amp-typescript-version
This includes
The text was updated successfully, but these errors were encountered: