Alex Malkevich

Hi, thanks for a great typings. There is just one thing about inputs - they are not 100% correct as its based on type information only and inputs may be...

I think if the type produced for inputs is more inclusive then just inputs then it's totally fine since devs still can assign inputs correctly and just have autocomplete on...

Hey, is there still any interest in this? If not I will close the issue at some point in the future.

Hey, thanks for providing reproduction repo - it was very useful to debug the issue! I have found the problem and it lays down in a way you process input...

I'm closing this issue as it's outdated and no fix is planned for it. If you want to reopen the discussion please feel free to open a new issue.

Hi, I see what's the issue. The thing is that `IoService` is private internal service that was not meant to be exposed as a public API. So that library basically...

@yjaaidi thanks for the feedback. I would like to help you to solve the problem but I'm failing to see what exactly `@wishtack/reactive-component-loader` is trying to do and thus what...

Hi @yjaaidi, Thanks for your clarifications. Now I checked the `wtLazy` directive and have clearer idea of how it's working. Regarding your proposed solutions to the issue: - Getting rid...

Oh I see. That's unfortunate... Well we can go around from the other side - extend `NgComponentOutlet` directive. Essentially you want your custom component resolution to be integrated with `ndcDynamicInputs/Outputs`...

Hey, not sure if it's relevant but since [v10.4.0](https://github.com/gund/ng-dynamic-component/releases/tag/v10.4.0) the `IoService` is now stable and part of public API. I'm closing this issue as it's outdated. If you want to...