Material UI: Ready-to-use foundational React components, free forever. It includes Material UI, which implements Google's Material Design.
MIT License
Big thanks to the 11 contributors who made this release possible.
As always, we are focusing on bug fixes but this time, we introduce an exceptional breaking change.
This change is paving the way toward supporting the upcoming react@16 release a.k.a Fiber.
The react-tap-event-plugin
dependency was removed, it was first introduced 3 years ago in order to remove the click delay on mobile devices.
Mobiles devices' browsers have improved since then, it's no longer required.
It's time to remove that dependency as we have done it a year ago on the v1-beta
branch.
You need to replace the onTouchTap
property callbacks with onClick
.
-<div onTouchTap={this.handleEvent} />
+<div onClick={this.handleEvent} />
Thanks @lostpebble for your hard work!
Big thanks to the 7 contributors who made this release possible.
Big thanks to the 8 contributors who made this release possible.
This release is full of bug fixes and documentation improvements following the major
styling update of the previous release.
Big thanks to the 12 contributors who made this release possible.
This is the first beta release.
We are proud to move to the next step after 7 months of dogfooding with the alpha releases.
We have been fixing many bugs and implemented new features.
The styling solution has also been greatly improved:
c1y
MuiThemeProvider
createStyleSheet
API with an optional namereact-jss
Please keep in mind that semver won't be respected between pre-releases.
In other words, the API will change if we need to.
The styleManager
is gone. The server side rendering configuration changed, use the sheetManager
instead. The documentation was updated, you can refer to it if needed.
Big thanks to the 11 contributors who made this release possible.
As always, we are focusing on bug fixes.
N.A
<RadioGroup>
- <LabelRadio label="Male" value="male" />
+ <FormControlLabel value="male" control={<Radio />} label="Male" />
</RadioGroup>
This change provides more flexibility.
- <BottomNavigation index={index} onChange={this.handleChange}>
+ <BottomNavigation value={value} onChange={this.handleChange}>
Also plan to do the same for the Tabs
in order to have a consistant API
where we always use value
/onChange
for controlled components.
<TextField
- marginForm
+ margin="normal"
/>
-import { blue, fullWhite } from 'material-ui/styles/colors'
+import blue from 'material-ui/colors/blue'
+import common from 'material-ui/colors/common'
+const { fullWhite } = common
Big thanks to the 7 contributors who made this release possible.
As always, we are focusing on bug fixes.
N.A
Do you like playing with bleeding edge tech?
We do, we have extended the support of React to the 16.0.0-alpha.13 release (aka Fiber).
Big thanks to the 17 contributors who made this release possible.
This release keeps focusing on bug fixes.
N.A
The previous v1.0.0-alpha.18 release is corrupted.
classes
property over the removed xxxClassName
.Big thanks to the 8 contributors who made this release possible.
-<Button contrast primary>Login</Button>
+<Button color="contrast">Login</Button>
Big thanks to the 22 contributors who made this release possible.
This release keeps focusing on bug fixes.
This release is mainly about bug fixes and improving the documentation.
Shout out to @kybarg for the update of the TextField
in order to better follow the spec (#6566).
false
as a valid index value (#6945) @oliviertassinariThis release introduces an important change in the API and the implementation.
Each exposed component is wrapped with a withStyles
Higher-order component.
This HOC has different responsibilities, the one you gonna be interested in is
regarding the classes
property. Now, we consider the CSS as a public API.
You now have two way to customize absolutely all the CSS injected by Material-UI.
Either the instance level with the classes
property or the class level with the
overrides
theme property.
To learn more about it, have a look at the documentation. Also, these options are automatically documented.
innerRef
or inputRef
.withResponsiveFullScreen
(#6898) @rosskevin