-
Notifications
You must be signed in to change notification settings - Fork 27.2k
Expose '_loadedConfig' in a public way. #24069
Copy link
Copy link
Open
Labels
area: routerfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under considerationrouter: lazy loading
Milestone
Metadata
Metadata
Assignees
Labels
area: routerfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under considerationrouter: lazy loading
I'm submitting a...
Current behavior
From a component that is loaded at bootstrap time I would like to dynamically instantiate a component that is loaded lazily on the current route. For that purpose I need access to the ComponentFactoryResolver for that route.
The only way I could find to access that resolver is via the private "_loadedConfig" property on the active route.
Expected behavior
I would like to be able to access the resolved via a public API, not relying on an implementation detail.
What is the motivation / use case for changing the behavior?
Better stability of my code by relying on public APIs, only.
Environment