This is a library for using Redux to manage state for self-contained apps in a Micro-Frontend architecture. Each self-contained isolated app can have its own isolated and decoupled Redux store. The componentized stores interact with a global store for enabling cross-application communication.
MIT License
344
stars
64
forks
source link
AppB is able to modify store in AppA that doesn't have registered global actions #25
I'm playing arround with this library and I found out that I'm able to update state from AppA -> AppB even if AppB doesn't have registered global actions.
I'm able to dispatch action from AppB to AppA and modify the 'MFAppStore' even if there are not registered global actions.
In documentation ( readme ) it says:
this.globalStore.DispatchAction("App1", action); // This will dispatch the action to current app's store as well other stores who might have registered 'Action-1' as a global action
but it seems that it doesn't work as it is intended or I'm missing something?
Describe the bug Hi everyone,
I'm playing arround with this library and I found out that I'm able to update state from AppA -> AppB even if AppB doesn't have registered global actions.
AppA:
AppB:
I'm able to dispatch action from AppB to AppA and modify the 'MFAppStore' even if there are not registered global actions.
In documentation ( readme ) it says:
this.globalStore.DispatchAction("App1", action); // This will dispatch the action to current app's store as well other stores who might have registered 'Action-1' as a global action
but it seems that it doesn't work as it is intended or I'm missing something?
Or it was always allowed?
Thanks