Miloš Lapiš

... hmm, do you have a plunker that implements the resolver? Because in your code I can't se where you use the resolver service. It should be related to a...

... for sure, it is logical. What to think using some identification of the module and then inject that value to the resolver service to know what module is processed...

Maybe yes, in some cases but actually you don't have it and doesn't seem that someting like that will get the support in near future. As I know there should...

Sure. The intention wasn't to say anything against, just a guess. 👀

@leak ... and `constructor` on a module level is not enough for you?

@leak ... oh, I thought `constructor` of `HomeModule` lazy loaded module ... it should be called only when that module is loaded, not earlier, certainly not when `LoginPageComponent` is instantiated.

@leak ... ah, you have that module as a default route ... so no surprise that it is loaded immediately ... `{ path: '', loadChildren: './home/home.module#HomeModule' }` but then its...

@shybaLen What such a syntax means concretely on the `` side? And what `otherInputs` and `otherOutputs` means on the host side?

@vecernik ... you can use ``.

@vecernik ... ah, so because of `controls` is a boolean attribute then something like ``?