sideNav: rename md-sidenav-layout

[ThomasBurleson]

Bug, feature request, or proposal:

Current implementation uses md-sidenav-layout as the smart container for content and md-sidenav components. The -layout suffix is ambiguous and conflicts with names and concepts for the Material Layouts API and features.

What is the expected behavior?

Please rename to md-sidenav-container

What is the current behavior?

What are the steps to reproduce?

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd

What is the use-case or motivation for changing an existing behavior?

The -layout suffix is ambiguous and conflicts with names and concepts for the Material Layouts API and features.

Which versions of Angular, Material, OS, browsers are affected?

Is there anything else we should know?

[jelbourn]

@hansl @kara any thoughts on this? I'm not convinced on the name change since we don't have any layout concepts in material2 for this to conflict with. I like the name now because I see it as more accurately capturing the intent of setting up a sidenav layout for your app (sidenav + main content area).

[hansl]

I'd rather have a proper layout engine in material2 and get rid of md-sidenav-layout. In the meantime, I agree with Thomas that container is more correct since it doesn't really affect layout.

[ThomasBurleson]

@jelbourn - Also Angular Layouts is in active development and will be ready in the fall for Angular 2 apps and Angular Material 2.

I highly recommend that ngM2 does not implement a layout engine. That effort is already underway and lead by Misko.

[jelbourn]

@mmalerba I want to follow up on this with some more discussion

[mmalerba]

Agreed with Thomas & Hans that container > layout. I'd also like to switch sidenav to drawer. A sidenav is only one possible use of the drawer component, so I propose: md-drawer-container and md-drawer

[mmalerba]

renamed to md-sidenav-container in #2183

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}