Dialog so complicated

[aminebizid]

First of all, chapeau bas @jelbourn for writing down this amazing dialog code.
But I don't understand why it's so complicated adding components dynamically with ng2
I think a piece of api like hereafter is missing:
let factory = getFactory(myCmp);
let cmp = factory.createInstance();
this.renderer.addChildComponent(this.htmlElement);

[fxck]

I personally like this API the best ng-bootstrap/ng-bootstrap#3 (comment) (and following discussion)

and it shouldn't even be that hard to make, since I've finally figured out how to use that portal / overlay combo #998 (comment)

[jelbourn]

We feel that a declarative API really doesn't make sense for components like dialog, snackbar, etc.

@Zigzag95 Saying the implementation is "too complicated" is not a bug, feature request, or proposal for Material. It's as complicated as it has to be to support AoT compilation.

[fxck]

@jelbourn I'd argue that for modal particularly it does

a) it's how the native dialog element will work https://developer.mozilla.org/en/docs/Web/HTML/Element/dialog
b) allows you to utilize state managment libs like @ngrx/store better, as it can practically be stateless

[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.}