-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Add support for MUI v6 #10439
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
Merged
Add support for MUI v6 #10439
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
e61b09f
Add support for MUI v6
djhi d2ca8b4
Fix yarn.lock
djhi 41aa489
Fix CRM demo
djhi de6f1cb
Fix useTheme tests
djhi 33818f1
Revert devDependencies to v5
djhi 92e0bc7
Fix remaining color props in demo
djhi 64a7ba3
Fix LocalesMenuButton
djhi f9fddb1
Fix yarn.lock
djhi d759c9f
Fix yarn.lock
djhi 6841225
Fix TagList
djhi 0a65b45
Fix ApplicationsDashboard
djhi a4703fd
Fix Labeled issue with color
djhi 19be517
Fix Labeled doc
djhi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Any changes in the CRM should be backported to https://github.com/marmelab/atomic-crm.
Besides, why do you need those changes? To my understanding, the MUI version used by the CRM demo shouldn't have changed, right?
UPDATE: I take it you kept those changes to prepare the compatibility with MUI v6, so I'm OK to keep them. But still, you'll need to open a PR to backport them to
marmelab/atomic-crm.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.
Those changes work in v5 too. We were using deprecated features that have been removed in v6. I'd rather address them now than forget them