Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our community
Top Pro
•••
Top Pro
•••Top Con
•••
Top Pro
•••Top Pro
•••
"Official Flux-Like implementation" - their own docs. They explain it better than I ever could, but I love separation of concerns, how modular it is and how everything can be shared and feed into each other without being concerned over how, where etc. https://vuejs.org/v2/guide/state-management.html#Official-Flux-Like-Implementation See More
Both the simplest and the most complex UI logic mixing-and-matching events from mouse, triggers, web sockets, button clicks can be implemented just by combining a few operators. Dramatically reduced code size, reduced surface for bugs and amount ot unit tests required for full coverage. See More
It's not trivial to use, especially for developers who haven't done any functional-reactive programming before, but it's a worth investment (ChatGPT can help finding the right operators to use, as there are plenty). Don't just try it if you're in a rush, but certainly do learn it as a longer-term investment. See More
Reducers are pure functions that returns the next state based on the previous state and an action (describing what should be changed). Since they are pure functions, they return a new state object instead of modifying the existing state. This ensures that it doesn't affect anything outside of the function's scope, making it free from unintended side effects and also makes debugging easier. See More
In Redux, the state of your application is held in a single object. The only way to change the state is to emit an action describing the change — there is no way to mutate state from the view, callbacks, or anywhere else. This makes the state of your application predictable and objective, and reduces the chances of any unintended state mutation by a callback somewhere else in your code. See More