-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[materiaul-ui][Typography] Deprecate paragraph
prop
#16926
Comments
It also applies margin bottom, just a bit difference from what |
This part of the Typography component is not pretty. I want to improve it since the release of v1. The documentation is not incorrect without being helpful. I would blame the implementation with the problem. I have personally almost never used the What API would you like to see? As we are working toward moving the system into the core component, we should be able to leverage the |
To be honest I'm not using I'm not sure if any API of this kind is required here. |
@keul How are you handling the spacing between two different Typography elements? |
I don't have much on them in my application right now, but I commonly use some |
Ok, thanks for sharing. |
I tend to use |
Is there any reason for this |
@buchanaf What do you mean by margin interface? Like |
@oliviertassinari, yes, exactly, including |
@buchanaf |
Ah, good to know. I look forward to it! Good luck with the rest and thanks for your work! |
paragraph
prop (use system instead)
We are deprecating the |
paragraph
prop (use system instead)paragraph
prop
A small documentation issue at page https://material-ui.com/api/typography/
At props section (https://material-ui.com/api/typography/#props): inside the table
paragraph
andgutterBottom
both reports If true, the text will have a bottom margin. which is confusing.I guess is the paragraph description that is wrong.
Edit by @oliviertassinari.
A proposal: we deprecate the
paragraph
prop as they are likely already covered by the system props, e.g.mb
.The text was updated successfully, but these errors were encountered: