north

4 ms·

1.
by north 9y ago
Thanks! Yeah, right now, state that shouldn't be saved (like computed properties) can be added as regular object properties (i.e. not a part of the initialState), and updated by listening for action events. I've been thinking of w
2.
by north 9y ago
Right, maybe I called out the wrong part of your example. redux-saga gives a really elegant way to describe the flow, but I feel at the expense of wrapping the async code with special helpers (call, put, fork, etc). You have to learn a few
3.
by north 9y ago
This example doesn't cover all the cases you're showing above, but in megalith or MST you would typically have a clearer separation between the functions that change state and the async communication parts. https://gith
4.
by north 9y ago
Yeah, if I was starting today I might end up with MST as well. The only real benefit of megalith right now would be its size (5k vs 45k). You do get more features for that size though, like integration with the Redux toolset.
5.
by north 9y ago
Shameless plug for another take on the same promise: https://github.com/jnorth/megalith I think most people who are attracted to Redux's core principals but want a more opinionated structure will end up gravitatin
6.
by north 13y ago
Koken might be an other alternative. http://koken.me
7.
by north 15y ago
Nice write-up. I think it could be a pretty interesting thing for people that don't interact via status updates very often, like me. Can you set permissions on the timeline per user/group?