My idea was more when you have completely different layouts like in the example.
You have your app layout and then you have a layout for login/register.
Which have not much in common
And yes then if you don't need the topbar it could be configured via routes too :)
Yup, especially in that case: I don't want to pull in the code for the login page module when the user is already logged in and won't hit the login page, if you see what I mean.
But anyway you're right, the cost is usually not that high with simple components like that.
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.
I mean, your layouts cannot be lazy-loaded (nor cascaded, which is a nice feature).
In my app, I have several levels of such layouts. Let's say you have a layout:
You can have a first layout:
and then in contents you can inject a layout with two router-outlets,
left-menu&page_contents.And the
left menu + contentslayout does not have to be loaded if you don't navigate to this part.I hope it's clear :)
Ahh okay yeah :D
Sure that's also not bad.
My idea was more when you have completely different layouts like in the example.
You have your app layout and then you have a layout for login/register.
Which have not much in common
And yes then if you don't need the topbar it could be configured via routes too :)
Yup, especially in that case: I don't want to pull in the code for the login page module when the user is already logged in and won't hit the login page, if you see what I mean.
But anyway you're right, the cost is usually not that high with simple components like that.