|
|
|
|
|
|
by btown
4173 days ago
|
|
|
I've found that contexts are a good way to handle this - they're basically invisible props that get implicitly passed down the component tree, and mixins can whitelist which parts of the context they want to be able to use. They're undocumented, but they're used quite widely in React, so I doubt they're going anywhere. You can have a top-level component instantiate new dispatchers and stores and expose them as i.e. "this.context.userStore", "this.context.dispatcher" to mixins and component code. And this can be done concurrently in the same Node process without needing VMs/sandboxing. Your state mixin API might need to change a bit, but it can be substantially the same: var UserState = Marty.createStateMixin({
listenTo: "UserStore",
getState: function (UserStore) {
return {
users: UserStore.getAll()
};
}
}); A reference: https://www.tildedave.com/2014/11/15/introduction-to-context... Fluxxor, FYI, bundles all of this in context.flux: https://github.com/BinaryMuse/fluxxor/blob/master/lib/flux_m... |
|
|