page-router-outlet include component

I am trying to include a component on every page. With regular angular I’d do it this way: <router-outlet></router-outlet><my-component></my-component> This works, but navigation back doesn’t work (this is to be expected) I cannot substitute router-outlet with page-router-outlet, because my-component isn’t present then (according to documentation, this is also expected behavior). Can you please suggest a solution? I asked on SO, but had no luck there also.

[orgbx]

Hey @lukashlobil, check this solution using angular’s content projection, it may fit your needs. It’s a shared component, showcase-layout.component, that wraps each page such as this one to have a more DRY solution. In this case, it receives a title and can have an optional extra-header content. It’s true that the component get’s “recreated” each time, but it’s unnoticeable (Let shared angular service handle the logic).

[lukashlobil]

Thank you for thorough response. I had to make sure I am not overlooking anything. So I basically had to hear: “you have to do it this way”. What gave me the drive to look into this deeper was the usage of router-outlet, which worked as I expected from web development (minus the back navigation) - I understand, in native terms when I used router-outlet and navigated, the content just got switched and no navigation took place. So when I pressed back, there was nothing in history and application closed itself. Makes sense. Thank you for taking the time to make it clear for me that this is “by design”.

(Would be a cool feature though)