RMWC Icon component
npm install @rmwc/iconMaterial icons use geometric shapes to visually represent core ideas, capabilities, or topics.
- Module @rmwc/icon
- Import styles:
- Using CSS Loader
- import '@rmwc/icon/styles';
- Or include stylesheets
- '@rmwc/icon/icon.css'
- MDC Docs: https://material.io/icons
Icons are not part of the official material-components-web spec, but they are referenced many times in the documentation. RMWC provides a declarative way to use icons. Note that RMWC does not ship with any icons of its own. Make sure you include an icon set! You can use any one you want, but Google's Material Icons are available through open source. Follow Google's developer guide to get them setup with your app. https://google.github.io/material-design-icons/
There are lots of different strategies for implementing icons on the web, and the Icon component is flexible for most of them. Use ligatures, classNames, inline SVGs, HTML, or URLs to get icons into your app. The default strategy is 'ligature' which works with the material.io font icon set.
The Icon component, (really the icon prop itself) can accept a variety of formats. Anywhere you see a component prop like icon or trailingIcon will inherit the same behavior.
``jsx`
`jsx`
background: 'green',
width: '24px',
height: '24px',
borderRadius: '100px'
}}
/>
}
/>
`jsx
<>
{/**
If you have additional options,
you can pass an object of options to the icon prop.
*/}
{/**
Passing additional props is especially helpful when the entire icon
component isn't exposed. In this example we pass the additional
onMouseOver prop directly to the icon
*/}
icon={{
icon: 'add',
onMouseOver: () => console.log('OVER')
}}
/>
`
The Material spec details multiple sizes for icons. The Icon component doesn't assign a size by default, but these are available to you to force a size. Please note, this will only work if you've included the RMWC icon css file.
`jsx`
<>
{/ 18px /}
{/ 20px /}
{/ 24px /}
{/ 36px /}
{/ 48px /}
This is for icon fonts that support ligatures like material-icons. This is the default strategy if nothing is set and doesn't require any additional setup if you are using material-icons.
`jsx`
<>
{/ Example showing how to set the strategy explicitly /}
This is for icons that are accessible via HTTP(S) and will be loaded directly into an img tag. This can be auto-detected for things that look like urls. The image will be set as a backgroundImage of the icon. Make sure you impor the RMWC icon css file for this to work properly.
`jsx`
<>
{/* Auto detection /}
{/* Explicit /}
icon: 'images/icons/twitter.png',
strategy: 'url'
}}
/>
This will render a child component inside of the icon. This is useful for all sorts of customization and for rendering inline SVGs. The following example shows rendering an SVG, as well as an arbitrary div.
`jsx`
<>
{/* Auto detection /}
background: 'green',
width: '24px',
height: '24px',
borderRadius: '100px'
}}
/>
}
/>
{/* Explicit /}
strategy: 'component',
icon: (
viewBox="0 0 24 24"
>
d="M21.35,11.1H12.18V13.83H18.69C18.36,17.64 15.19,19.27 12.19,19.27C8.36,19.27 5,16.25 5,12C5,7.9 8.2,4.73 12.2,4.73C15.29,4.73 17.1,6.7 17.1,6.7L19,4.72C19,4.72 16.56,2 12.1,2C6.42,2 2.03,6.8 2.03,12C2.03,17.05 6.16,22 12.25,22C17.6,22 21.5,18.33 21.5,12.91C21.5,11.76 21.35,11.1 21.35,11.1V11.1Z"
/>
)
}}
/>
Some font icon sets like Ion Icons and Glyph Icons render based on a className that is set. RMWC docs doesn't include extra icon fonts so there is no example to render, but the below code should give you an approximation.
THIS CANNOT BE AUTO DETECTED. You'll have to explicitly set the strategy directly on the Icon or specify it globally via the RMWCProvider.
`jsx`
<>
{/ Ion Icons /}
icon: 'star',
strategy: 'className',
basename: 'icon',
prefix: 'ion-'
}}
/>
{/**
* Set the option globally throug RMWCProvider
* Glyphicons
**/}
strategy: 'className',
basename: 'glyphicons',
prefix: 'glyphicons-'
}}
>
Sometimes, you just need to do your own thing. Maybe you have a legacy project that already has icons and you want to incorporate them with RMWC. If none of the other strategies are what you need, then you can hijack the whole thing and delegate it to your own render function.
`jsx`
icon: 'favorite',
strategy: 'custom',
render: ({ content }) => Hello + {content}
}}
/>
A more relevant example involves an app that has a custom / existing icon component. There are a litany of reasons why your app might need one, but if you've found this section of the docs you likely know what problem you need to solve.
`jsx
// 1) Your app has an icon component you use
import { MyIconComponent } from '@rmwc/icon';
// 2) Now you are using RMWC, lots of components are instances of Icons
// You need to be able to delegate the handling of an icon prop to your own component
import { TextField } from '@rmwc/textField';
import { Chip } from '@rmwc/chip';
// 3) Instead, you should set the custom strategy to be your default
// and add your own handling with RMWCProvider
import React from 'react';
import * as ReactDOM from 'react-dom';
import App from './App'; // your main app component
import { RMWCProvider } from '@rmwc/provider';
import { MyIconComponent } from '@rmwc/icon';
const iconRenderHandler = ({ content, className, ...rest }) => {
// content is whatever was passed to the icon prop
// className is the fully processed className taking into account the basename and prefix defaults
// it's important to include this because MDC often has classes like text-field-icon directly
// on the component for alignment
// rest is just any other props
return
};
ReactDOM.render(
document.getElementById('root')
);
// 4) Now anywhere in your app that an Icon instance is used, it will be
// delegated to your handler and render your custom component
import { TextFieldIcon } from '@rmwc/textfield';
`
| Name | Type | Description |
|------|------|-------------|
| icon | IconPropT` | The icon to use. This can be a string for a font icon, a url, or whatever the selected strategy needs. |