'What is the use case for dynamic component loading?
I am having a little trouble understanding what the use case is for dynamic component loading. The explanation from the ng docs states:
An application might need to load new components at runtime.
Could you not handle this scenario with an ngSwtich that then loads a child-component? Or is the use case for components that are not even bundled with the app that can be loaded dynamically at runtime? So in this case the component is run through the Angular compiler at runtime and compiles the component dynamically, then injecting the compiled component into the running application, or?
Aside from the technical side of this, when would this be necessary? Don't you normally have dynamic data feeding a component rather than having dynamic components inserted into a dom node? Maybe I am just lacking creativity, but I can not see when dynamically loading a component would be necessary.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|