Tabs + Routing

[jelbourn]

This captures using tabs (or a tab-like ui) with routing.

[apals]

Any ETA on this?

[naveedahmed1]

It would be really nice to have md-tabs linked with router.

[aminebizid]

You mean with async routing and a nice progress circle while getting data. Yeah it will be great.

[DennisSmolek]

So I was wondering why build the routing directly into the component? With so many routers out there (Core, Beta, UI, ngrx, ionic) wouldn't it be better to just have the tabs component emit events and allow the user to attach to it?

Instead of doing <md-tabs><md-tab [router-link]="['/whatever',"1234"]"></md-tab></md-tabs> you would do: <md-tabs><md-tab (tabNavigate)="doRouterAction(navData)"></md-tab> or even: (tabNavigate)="router.location(event)"

for progress you could do: [nav-progress]="getNavProgress()"

This way the tabs stay flexible for dev's to use the router of their choice..

you could even attach the event on just the main <md-tabs> and keep the rest clean...

[jelbourn]

It's just tabs that have a routing outlet in them and the "tabs" are anchors.

[DennisSmolek]

That's true, I wasn't thinking about the outlet being built in...

[kyleledbetter]

Probably obvious, but if tabs are used as a router (or regardless), it would be nice to conditionally not render the <div class="md-tab-body-wrapper">

https://github.com/angular/material2/blob/master/src/components/tabs/tab-group.html#L17-L25

[aminebizid]

@jelbourn you are ok for a PR implementing md-tab-routed or you prefer upgrade actual md-tab?

[jelbourn]

@robertmesserle is already working on this.