docs: named imports

Description In the docs, the import of the module in the same namespace has been done using multiple import statements.

Current behaviour

import AppBar from '@material-ui/core/AppBar';
import Toolbar from '@material-ui/core/Toolbar';
import Typography from '@material-ui/core/Typography';
import Button from '@material-ui/core/Button';

Proposed Behaviour

import {AppBar, Toolbar, Typography, Button} from '@material-ui/core';

Why so Named imports help to keep track of imports from a specific package, as well as makes code a bit cleaner.

Let’s discuss: loudspeaker:

[mbrookes]

I was on the fence here. I like the idea of demonstrating simplified imports for core, but I can understand the concern about “it depends” in general for icons.

On reflection, my gut feeling is that if the demos use differing approaches for core and icons, less experienced developers will follow the pattern shown, while more experienced developers will understand the difference.

[eps1lon]

People copy & paste the demos.

Some actually write code themselves and don’t just copy&paste their apps.

We could document the best tradeoff in the demos and add a FAQ section about the difference?

Yeah like that worked in the past. It didn’t even work for this issue that got opened without any mention of the documented trade-offs.