Closed jcperez-ch closed 8 years ago
Response to this question, after research. Yes... the way mcfly handled the action dispatching was asynchronous, because it assures a resolve/reject via a promise. You can have actions that instead of returning an action descriptor, returns a promise with a resolving/rejecting action descriptor.
To preserve that functionality we included a second parameter in flaxs.createActions
method, explained in PR 13
Unit tests added as well, synchronous flags are used in version 1.0.4
The idea is to avoid the asynchronous gap between the action call and the store change.
We need deeper research on different posibilities: