The new Container implementation is lazy by default (does not create a store until a subscriber asks for it) but current implementation allows container to be mounted as sibling to initialise global stores.
So we add a test to ensure we still support this use case. That also found another scenario where isGlobal stores might get cleaned up accidentally
The new Container implementation is lazy by default (does not create a store until a subscriber asks for it) but current implementation allows container to be mounted as sibling to initialise global stores.
So we add a test to ensure we still support this use case. That also found another scenario where
isGlobalstores might get cleaned up accidentally