yarn material-ui 1.0.0-beta.31
on Node.js Yarn

latest releases: 0.20.2, 0.20.1, 1.0.0-beta.47...
6 years ago
Jan 21, 2018

Big thanks to the 14 contributors who made this release possible.

Here are some highlights ✨:

Fun facts:

  • Our first alpha release was 1 year ago: Jan 28, 2017 🎂!
  • We have done 53 pre-releases of the v1.x, one every week for a year 🛥.

Breaking change

We have removed the "magic" <Icon> wrapping logic. It should be done explicitly now.
It's making our components less biased around the svg icon vs font icon choice. 

+import Icon from 'material-ui/Icon';

-      <IconButton>comment</IconButton>
+      <IconButton>
+        <Icon>comment</Icon>
+      </IconButton>

  • [theme] Further simplification & standardization (#10015) @mbrookes

    • Most component specific theme.palette.background colors have been removed. The affected components use theme.palette.grey instead. Shift the values of theme.palette.grey if you wish to lighten or darken these as a whole; this will maintain the contrast relationship between them. (Paper remains in the theme, as it is used across multiple components.)
    • theme.palette.common.fullBlack and fullWhite have been removed. Components that used these values now use theme.palette.common.black and white instead.
    • theme.palette.common.transparent has been removed. Components that used this value now use 'transparent' directly.
    • Chip has been corrected to use theme.palette.grey. If you have customized the values of grey, the appearance of Chip in your app may change.

  • [core] Remove the rootRef properties as unneeded (#10025) 

-import ReactDOM from 'react-dom';

<IconButton
- rootRef={node => {
-   this.button = ReactDOM.findDOMNode(node);
+ buttonRef={node => {
+   this.button = node;
  }}
>
-<Button dense>
+<Button size="small">

In order to keep the palette simple to understand, we have removed the types from the palette object.
The motivation is the following. The theme & palette should only store
the information needed to display one UI context.
Having the types object in the palette encourage people to rely on it.
No, we want people to do it the other way around.

For instance, instead of doing: 

const theme = createMuiTheme({
  palette: {
    type: 'dark',
    types: {
      dark: {
        background: {
          default: '#000',
        },
      },
      light: {
        background: {
          default: '#fff',
        },
      },
    },
  },
});

We would rather see people doing: 

const types = {
  dark: {
    background: {
      default: '#000',
    },
  },
  light: {
    background: {
      default: '#fff',
    },
  },
};

const theme = createMuiTheme({
  palette: {
    type: 'dark',
    ...types.dark,
  },
});

Component Fixes / Enhancements

Docs

Core

Check out latest releases or
releases around material-ui 1.0.0-beta.31

Don't miss a new material-ui release

NewReleases is sending notifications on new releases.

Get notifications