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
I would expect that doing rebinds in container modules would actually save the replaced service and when the container module is unloaded it would put back the previous service. My use case is a service that stores context data and this is used in react with router and on some subpath I need to extend the context. I use a container module on that path to load a different context. The issue is when I go back to a previous path I need to unload the module and this fully removes the context service.
Current Behavior
Currently on module unload the service is completely removed.
Possible Solution
Keep a stack of bounded references for that type and on unloads called for container modules pop the stack and set back to old service.
The text was updated successfully, but these errors were encountered:
Expected Behavior
I would expect that doing rebinds in container modules would actually save the replaced service and when the container module is unloaded it would put back the previous service. My use case is a service that stores context data and this is used in react with router and on some subpath I need to extend the context. I use a container module on that path to load a different context. The issue is when I go back to a previous path I need to unload the module and this fully removes the context service.
Current Behavior
Currently on module unload the service is completely removed.
Possible Solution
Keep a stack of bounded references for that type and on unloads called for container modules pop the stack and set back to old service.
The text was updated successfully, but these errors were encountered: