[docs] Document that @emotion/react is not fully supported in the System
#31825
Conversation
This file contains 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
2 tasks
|
Let's see first whether is worth fixing it, before documenting it. |
danilo-leal
changed the title
@emotion/react is not fully supported in the System
|
Fixed by #33205 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello!
Currently it's not really possible to use
@emotion/reactto write custom styles for MUI.More precisely it is possible to use
classNameand thecssproperty but not theclassesprop that the MUI component provides.The reason for that is that the internal styles will always take precedence over the custom styles unless users explicitly increase specificity using
!importantor&&which is not an acceptable solution.As detailed here there is no way for the user to configure it's project to change this state of things.
I have opened an issue about it some time ago but for reasons that I perfectly understand you decided not to address it.
Considering this, I think it is best, to save users frustration, to let them know that
@emotion/reactis not really supported.