[system][docs] Clarifying differences between JSS- and Emotion-based `styled` utilities
@mnajdova is already working on this.
Since Oct 11, 2023.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Duplicates
- I have searched the existing issues
Related page
https://mui.com/material-ui/migration/v5-style-changes/#styled
Kind of issue
Unclear explanations
Issue description
I was looking for ... and it appears that ...
I was looking into how to create reusable styled components. It appears that there are a couple of places from which I can import the utility fn, but it is not clear which is the correct one (or if all are the same?).
Migration guide says to change any usages of
-import { styled } from '@mui/material/styles';
+import { styled } from '@mui/styles';
But...
- documentation for
@mui/stylesstates that this is a legacy api. - documentation for
styledstates to use@mui/material/styles - tangential documentation uses
@mui/material/styles
From the amount of ocurrences, seems like migration docs is outdated. Maybe its the same under the hood? Could anyone shed some light here? Thanks!
Context 🔦
I just migrated a project from v4 to v5.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.