yeah this could be also a valid workaround too. If every (lazy-loaded) page has its own header/content/footer then this would be a valid option.
In my projects I mostly want to have the header only once created in a root (or the App itself) and under that header, comes the <router-outlet></router-outlet>.
But yeah then comes the niche-issue "I want to have a different header just for this one route".
Also this was just one example for those dynamic layouts there probably many more, which I haven't encountered yet, but probably will help me in the long run :D
Understood, that design requires a smart overideable header component. Something easily done using Event services. But will still require notification when other header is wanted.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey!
yeah this could be also a valid workaround too. If every (lazy-loaded) page has its own header/content/footer then this would be a valid option.
In my projects I mostly want to have the header only once created in a root (or the App itself) and under that header, comes the
<router-outlet></router-outlet>.But yeah then comes the niche-issue "I want to have a different header just for this one route".
Understood, that design requires a smart overideable header component. Something easily done using Event services. But will still require notification when other header is wanted.