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
{{ message }}
Repository navigation
How to communicate with Redux/MobX/Other State management tools elegantly. #610
In my case, I create a service to collect the events and states, and notify the redux. I like the current state management, although it is a little bit strange to some react developers. It is flexible enough, more detailed documentation on it would be nice.
In my case, I create a service to collect the events and states, and notify the redux. I like the current state management, although it is a little bit strange to some react developers. It is flexible enough, more detailed documentation on it would be nice.
The events and states are in one service, is the service too complex? We separate the States and Events via the Controller layer.
I mainly use your mode to manage states(service and controller with global DI) in project developed with molecule, and I like that.
I have some modules with old codes which use redux, so I make a service to do the communication between existing redux module and services in molecule(not all service states, only what I need). I love the current molecule's architecture, by using extensions and molecule services, it is facile to make extension modules with different tech stacks.
I mainly use your mode to manage states(service and controller with global DI) in project developed with molecule, and I like that.
I have some modules with old codes which use redux, so I make a service to do the communication between existing redux module and services in molecule(not all service states, only what I need). I love the current molecule's architecture, by using extensions and molecule services, it is facile to make extension modules with different tech stacks.
Your feedback is very important to us. we are planning to extract this architecture into a separate package, and it can be used for other React projects. Maybe we can keep in touch, lol~
Activity
hepezu commentedon Jan 15, 2022
In my case, I create a service to collect the events and states, and notify the redux. I like the current state management, although it is a little bit strange to some react developers. It is flexible enough, more detailed documentation on it would be nice.
wewoor commentedon Jan 17, 2022
The events and states are in one service, is the service too complex? We separate the States and Events via the Controller layer.
hepezu commentedon Jan 20, 2022
I mainly use your mode to manage states(service and controller with global DI) in project developed with molecule, and I like that.
I have some modules with old codes which use redux, so I make a service to do the communication between existing redux module and services in molecule(not all service states, only what I need). I love the current molecule's architecture, by using extensions and molecule services, it is facile to make extension modules with different tech stacks.
wewoor commentedon Jan 21, 2022
Your feedback is very important to us. we are planning to extract this architecture into a separate package, and it can be used for other React projects. Maybe we can keep in touch, lol~
#622
hepezu commentedon Jan 29, 2022
Happy Spring Festival.
Sure, keep in touch, I would like to make a demo in the future.