Releases: react-toolbox/react-toolbox
Releases · react-toolbox/react-toolbox
0.13.1
This release includes changes in React Toolbox file structure adopting a new convention. Fixes #98 . Now index.js
files inside each component's folder is only importing components and subcomponents instead of holding implementation. There is a match between files and components so each file is named the same as the component meaning that now you can import them directly: import Button from 'react-toolbox/lib/button/Button'
.
New Components
- We have a brand new
Card
component! way more flexible than it used to be. You can compose your own Cards by aggregating subcomponents such asCardTitle
,CardMedia
,CardActions
orCardText
. Fixes #115 and #95 (Thanks @nathanmarks!) - New
Avatar
component. You can either define an Image, a FontIcon, custom SVG icon or simply a letter as avatar. Internally they are only used in the Card component but soon they will be available in other components likeList
. - We extracted an
IconButton
from the regularButton
component and removed thetoggle
property. The API is the same as for the button but more limited since you can't have raisedIconButton
. Fixes #149
Breaking changes
- Since now we have an
IconButton
, theButton
withtoggle
property is deprecated. - Now there are no
loading
cards or buttons since they are not in Google Spec. Fixes #152 Tooltip
component now works as a decorator. This means you no longer have the tooltip properties available inInput
andButton
components among others. Instead you can decorate any component with theTooltip
and get a new component with Tooltip's properties. Check the docs for more info.- Now all input components pass the new value in the
onChange
callback. In previous versionsCheckbox
,Switch
,Input
and others were giving theevent
straight into the callback. Now they are passing the new value. - We left Material Design Icons out of the css import. It's not a good practice to include vendor imports in our stylesheet so we removed them. Now you have to import the font via Google Fonts as specified here. You can still use the
FontIcon
but remember to import the font. The name of the icon in the component should correspond to the imported icon:
<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">
- For the same reason, Roboto font import was removed too. You'd need to add an import for the font in a similar way to the font icon. Remember the font-weights we use:
300
,400
,500
,700
.
<link href="https://fonts.googleapis.com/css?family=Roboto:300,400,500,700" rel="stylesheet">