-
Notifications
You must be signed in to change notification settings - Fork 64
Consider Reflux replacement #28
Comments
Another option is to completely ditch React and move to CycleJS (project will be renamed to JS starter :) ) |
Relevant links: acdlite/flummox#63 Reflux doesn't normally support isomorphic JS (fail). They propose some ugly hacks but I don't care. |
Another interesting one is Baobab. Quote:
|
Transition to Baobab in progress. Please help to deal with forms: |
Beta version of Baobab branch is released. |
Not so much. All complexity is exposed there now and can easily be refactored later.
It's not a call. It's a declaration.
Environment. Browser or Node.js. We need to rethrow all errors besides HTTP. Otherwise they will be swallowed and fail silently.
It's meant to be called from detail / edit pages to load exactly one model by id.
Error. Need to fix. |
I don't get how removal can cause item addition. Please rephrase this whole question. |
Thank you! About removing Component, that use this data, will be updated. Is it correct? |
Yes |
I'm getting tired of Reflux. They seems to be really lost in what they do. Actions are flawed.
Candidates to watch and replace:
Flummox
Minimal Flux
Rx-Flux
ThunderCats (remix of the prev one)
Both are better then Reflux. I like API of the second one more, but it doesn't support async actions at this moment. It's better to wait a bit and see what will happen next.
The text was updated successfully, but these errors were encountered: