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

[docs] Make CSS interoperability examples easier to use #20860

Merged
merged 3 commits into from
May 3, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/src/pages/guides/interoperability/interoperability.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,7 @@ Nothing fancy, just plain CSS.
```jsx
import React from 'react';
import Button from '@material-ui/core/Button';
import './PlainCssButton.css';

export default function PlainCssButton() {
return (
Expand Down Expand Up @@ -93,6 +94,7 @@ The following example overrides the `label` style of `Button` in addition to the
```jsx
import React from 'react';
import Button from '@material-ui/core/Button';
import './PlainCssButtonDeep.css';

export default function PlainCssButtonDeep() {
return (
Expand Down Expand Up @@ -132,6 +134,7 @@ Explicitly providing the class names to the component is too much effort?
```jsx
import React from 'react';
import Button from '@material-ui/core/Button';
import './GlobalCssButton.css';

export default function GlobalCssButton() {
return <Button>Customized</Button>;
Expand Down