Here's a working example of the bug: https://codesandbox.io/p/sandbox/5dxt68.
It presents two scoped instances of two scoped molecules A and B where B depends on A.
In the first context B is explicitly mounted (via a useMolecule) whereas A is implicitly instantiated (via a mol molecule getter in B). If A is later explicitly mounted (via a useMolecule) within the same scope as B, A is instantiated a second time, and the controls to manipulate A's state do not invalidate B's state.
In the second context, both A and B are explicitly mounted (viauseMolecule) within the same scope. In this case, controls to manipulate A's state invalidates B's state.
Here's a working example of the bug: https://codesandbox.io/p/sandbox/5dxt68.
It presents two scoped instances of two scoped molecules A and B where B depends on A.
In the first context B is explicitly mounted (via a
useMolecule) whereas A is implicitly instantiated (via amolmolecule getter in B). If A is later explicitly mounted (via auseMolecule) within the same scope as B, A is instantiated a second time, and the controls to manipulate A's state do not invalidate B's state.In the second context, both A and B are explicitly mounted (via
useMolecule) within the same scope. In this case, controls to manipulate A's state invalidates B's state.