Feature: Enable nesting page router outlets

[MartoYankov]

With nativescript-angular 6.0 we will enable sibling named page-router-outlet at root level to enable the scenario with root TabView with navigations inside the tabs. This scenario is demonstrated in the template - https://github.com/NativeScript/template-tab-navigation-ng.

We would like to also support nested sibling named page-router-outlet. This will enable more scenarios with PROs that are now only possible with NG . Here are two scenarios:

1. Having a root page-router-outlet (PRO) that initially navigates to a Login page and upon login, navigates to a TabView with nested PRO navigations:

• PRO
  • Login
  • Tabs
    • PRO: Tab 1 Master --> Tab 1 Detail
    • PRO: Tab 2 Master --> Tab 2 Detail

2. Having a root RadSideDrawer that can switch between regular pages and TabView with nested PRO navigations:

• RadSideDrawer
  • PRO
    • Page 1 Master --> Page 2 Detail
    • Tabs
      • PRO: Tab 1 Master --> Tab 1 Detail
      • PRO: Tab 2 Master --> Tab 2 Detail

[YvesCandel]

Any estimation on how complicated this feature is?

[manojdcoder]

@NickIliev / @vakrilov / @sis0k0 Are we depended on Angular to fix any issues on their end to complete this feature? Just curious, as I'm aware that there are few issues with Angular's router when nesting named outlets.

[Bolhy10]

@NickIliev @sis0k0 @vakrilov ???

[IAMtheIAM]

This is a greatly desired feature. In fact it is not desired, it is fundamentally necessary to create any kind of functional business application, most of which require some form of authentication/authorization through login before accessing the application.

In order to use NativeScript on the job, this feature is required.

[NickIliev]

@IAMtheIAM @Bolhy10 @manojdcoder @YvesCandel thank you guys for your feedback. Indeed, we are aware that this feature is highly desirable and we are planning it for the next release of nativescript-angular. We will post all related updates here.

[IAMtheIAM]

@NickIliev That's great news! Thanks for the update. When the feature is available, I wonder if it is more appropriate to use an actual tabview component like being requested, or if its better to simulate a tabview and create normal page outlets using buttons styled like a tabview. What do you think?

[gbaldeck]

That's awesome @NickIliev. Will it be in {N} 4.2 or a later version?

[tskweres]

Awesome! +1 for lazy loading the tab views too :)

[NickIliev]

@gbaldeck the 4.2 release is a few days away and this feature is not ready and is still in the planning phase. I am sorry if I had misled anyone about the release date - the feature is planned for the 4.3 but still, in the end, it all depends on the complexity of the feature.

[gbaldeck]

@NickIliev In the meantime is there a workaround for having Tabs work with the RadSideDrawer?

[tskweres]

@gbaldeck @NickIliev I could try making a test app using just and not that has parents and children:

Login (eager)
Tabs (eager)
-- Tab one (lazy) (aux named outlet)
-- Tab Detail one
-- Tab two (lazy) (aux named outlet)
-- Tab Detail two

But - i'm curious if the page and header transitions, back button etc will still work as expected.

re: angular/angular#10981