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
This type of functionality should definitely be brought into traditional FLUX architecture. I built a framework called "Cerebral", which has a "one way" flow like flux, but instead of a dispatcher it uses an implementation called "signals". This keeps complete control of the state flow. Behind the signals is an immutable store, which also is an important part of being able to go "back and forth" in time.
Hi there!
This type of functionality should definitely be brought into traditional FLUX architecture. I built a framework called "Cerebral", which has a "one way" flow like flux, but instead of a dispatcher it uses an implementation called "signals". This keeps complete control of the state flow. Behind the signals is an immutable store, which also is an important part of being able to go "back and forth" in time.
Would love to share more stuff if you are interested. Here is a clip showing off the debugger of cerebral and here is the repo: https://github.com/christianalfoni/cerebral
The text was updated successfully, but these errors were encountered: