Add NgModule support to ngComponentOutlet

[mhevery]

@Component({
  template: `
   <ng-container *ngComponentOutlet="child?.component; ngModule: child?.moduleFactory"></ng-container>
`
}) 
class MyApp {
   child: {component: Type<any>, moduleFactory: NgModuleFactory<T> };
}

[mhevery]

/cc @jasonaden

[DzmitryShylovich]

@mhevery what is the use case? A component must be a part of a module or ngc will throw an error during compilation. So what's the purpose of moduleFactory arg? We will be able to create a component in the context of a different module?
Plus it's not user friendly syntax. In jit it have to be NgModule and in aot it have to be NgModuleFactory. We already faced a similar issue with router #14005 So we need a tool for automatic conversion.

[mhevery]

@DzmitryShylovich Let me clarify

1. yes Type can only be part of TypeFactory otherwise ngc would have an issue.
2. Both AoT and JIT should always behave same in the API, and this does not change that.
3. The change would allow the ngComponentOutlet to dynamically load a module into existence and then load a component from the that module.
4. The use case is if someone wants to lazy load code, and then add the lazy loaded code into the page using ngComponentOutlet.

[DzmitryShylovich]

@mhevery

Both AoT and JIT should always behave same in the API, and this does not change that.

but we don't have NgModuleFactory in jit, do we?

[mhevery]

but we don't have NgModuleFactory in jit, do we?

Yes we do: https://angular.io/docs/ts/latest/api/core/index/Compiler-class.html

[DzmitryShylovich]

I've got it. Thx.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}