Skip to content
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

Updated CHANGELOG.md and package.json for v0.8.0 prerelease #587

Merged
merged 2 commits into from Apr 27, 2015
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
34 changes: 34 additions & 0 deletions CHANGELOG.md
@@ -1,3 +1,37 @@
## 0.8.0 (Pre-release)
###### _TBD_

##### Breaking Changes
- Refactored all CSS into Javascript (#30, #316)
- All Material-UI components now have their styles defined inline. This solves
many problems with CSS as mentions in [@vjeux's presentation](https://speakerdeck.com/vjeux/react-css-in-js)
such polluting the global namespace with classes that really should be
component specific. In addition to the benefits mentioned in the
presentation, inline styles allow Material-UI to become CSS preprocessor
agnostic and make Themeing much more dynamic and simple.
[Read our CSS in JS discussion](https://github.com/callemall/material-ui/issues/30)
- Upgrade path:
- *If you are overriding component CSS classes:* Redefine your overrides as
an object following [React's inline styles format](https://facebook.github.io/react/tips/inline-styles.html),
then pass it into the material-ui component via the `style` prop. These
changes are applied to the root element of the component. If you are
overriding a nested element of the component, check the component's
documentation and see if there is a style prop available for that nested
element. If a style prop does not exist for the component's nested element
that you are trying to override, [submit an issue](https://github.com/callemall/material-ui/issues/new)
requesting to have it added.
- *If you are using any of Material-UI's Less files:* These files have been
refactored into their [own javascript files](https://github.com/callemall/material-ui/tree/css-in-js/src/styles)
and can be accessed like so `var FILENAME = require('material-ui').Styles.FILENAME;`.
Material-UI has moved away from being a CSS Framework to being simply a
set of React components.

##### General
- Themes have been added (#202)
- Requiring individual components is now supported (#363)
- An example would be: `var SvgIcon = require('material-ui/lib/svg-icon);`
- The `/lib` folder in Material-UI contains the file structure needed when referencing individual components.

## 0.7.4
###### _Apr. 21, 2015_

Expand Down
2 changes: 1 addition & 1 deletion docs/package.json
@@ -1,6 +1,6 @@
{
"name": "material-ui-docs",
"version": "0.7.4",
"version": "0.8.0",
"description": "Documentation site for material-ui",
"repository": {
"type": "git",
Expand Down
2 changes: 1 addition & 1 deletion package.json
@@ -1,7 +1,7 @@
{
"name": "material-ui",
"author": "Call-em-all Engineering Team",
"version": "0.7.4",
"version": "0.8.0",
"description": "Material Design UI components built with React",
"main": "./lib",
"scripts": {
Expand Down