Following on from my previous post on dynamic routing fundamentals, the ability to route dynamically across angular elements, i.e. to use the router to route to a dynamically loaded angular element, seems to be a sticking point.<\/p>\n
Previously, I developed a web components example where a ‘fabric’ component was responsible for dynamically creating web components and displaying them. This did not use angular routing, but dynamically added them to the dom based on menu selections or url parameters. Subsequently, I wanted to investigate whether I could use angular routing to implement this instead.<\/p>\n
I have found a number of examples of varying degrees of complexity, which go at least some of the way. However, I have not seen what I would term a reasonably straightforward, out-of-the-box solution, which does not involve too much deep diving into the internals of angular.<\/p>\n
The following examples have been examined to date:<\/p>\n
A complex dynamic one here with perhaps useful ideas but actual components still appear to be declared in the angular app: Some specific ideas in this one here but still some way to go IMO…
https:\/\/medium.com\/ngconf\/dynamic-component-generation-in-lazy-loaded-routes-d2e0f9e89c57<\/a>
The code is here:
https:\/\/github.com\/theAlgorithmist\/Angular8LazyLoadDynamic<\/a><\/p>\n
https:\/\/medium.com\/@timon.grassl\/how-to-use-routing-in-angular-web-components-c6a76449cdb<\/a><\/p>\n