[core] Remove makeStyles from @material-ui/core#26382
Conversation
|
@dtassone we have this regression - https://www.argos-ci.com/mui-org/material-ui/builds/3599 after upgrading to |
|
@eps1lon @oliviertassinari what shall we do with notistack still using |
| "@fortawesome/react-fontawesome": "^0.1.11", | ||
| "@material-ui/core": "5.0.0-alpha.34", | ||
| "@material-ui/data-grid": "^4.0.0-alpha.21", | ||
| "@material-ui/data-grid": "^4.0.0-alpha.29", |
There was a problem hiding this comment.
This is needed, as this version does not use makeStyles from @material-ui/core/styles anymore.
| width: 160, | ||
| valueGetter: (params) => | ||
| `${params.getValue('firstName') || ''} ${params.getValue('lastName') || ''}`, | ||
| `${params.getValue(params.id, 'firstName') || ''} ${ |
There was a problem hiding this comment.
This was a breaking change.
| } | ||
| ``` | ||
|
|
||
| Note: If you would like to move |
There was a problem hiding this comment.
Cleanup, was some leftover forgotten
|
Happy to go with whatever is the best. Option 1 seems to allow us to move fastest, but I am ok with any of the options. We could disable the example now and re-enable once |
Yes but looking at it now, I don't think it's great. We have largely enough space to render the title, it looks empty, and you wonder why the col title is not there or is cut as in the image below. |
Agree, maybe would be better if the toolbar (the icons) is rendered as some popover |
|
@dtassone I've increased the width of the columns by 20, it looks better now: We can update the example with the next release once this is fixed. |
Ideally just rewrite an import if that's possible. It's a good test whether the migration story is viable. |
Rewrite import + add |
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Where does |
I am creating it with |
We can rewrite this with babel in our repo. We're already doing a bunch of rewrites: So it sounds like we should be able to add the new one for compat if that is all required for migrating |
How can we do this, if only some of the imports from a package should be changed, for example: -import { makeStyles } from '@material-ui/core/styles';
+import { makeStyles } from '@material-ui/styles';
// but these should still be imported from @material-ui/core/styles
import { Theme, ThemProvider } from '@material-ui/core/styles'; |
|
sigh yeah, nevermind. The migration story is just all over the place unfortunately. |
makeStyles from @material-ui/core/stylesmakeStyles from @material-ui/core


BREAKING CHANGE
The
makeStylesJSS utility is no longer exported from@material-ui/core/styles. You can use@material-ui/styles/makeStylesinstead. Make sure to add aThemeProviderat the root of your application, as thedefaultThemeis no longer available. If you are using this utility together with@material-ui/core, it's recommended you use theThemeProvidercomponent from@material-ui/core/stylesinstead.