You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this works from the service assembly perspective, this causes M3.configure to be called twice (or rather N times, one time for each module it overrides). If configure defines its own services, they are loaded twice, causing exceptions.
The same issue happens if the modules are loaded via providers (as opposed to loaded explicitly per example above). One M3 instance is created, but its configure is called multiple times.
The text was updated successfully, but these errors were encountered:
The following setup creates an injector where one module overrides different services in more than module:
While this works from the service assembly perspective, this causes
M3.configure
to be called twice (or rather N times, one time for each module it overrides). Ifconfigure
defines its own services, they are loaded twice, causing exceptions.The same issue happens if the modules are loaded via providers (as opposed to loaded explicitly per example above). One M3 instance is created, but its
configure
is called multiple times.The text was updated successfully, but these errors were encountered: