Thanks for the article. I want to know your thought in regards to circular dependency warning on angular-cli project with reference to dynamic components.
We have followed a similar approach for creating our dynamic components, wherein we have CreateDynamicComponent service that does the job for us. We have component A which requires component B to be created dynamically and B which requires A to be created dynamically this is resulting into a warning through by Webpack. I want to understand your thoughts if these approach can have any negative impact on the application in future. What would the best solution to mitigate this ?