|
|
|
@ -3486,6 +3486,8 @@ and it creates a new state. This process is very easy to reason about and is
|
|
|
|
|
also very easy to test using unit tests. Please read the [redux
|
|
|
|
|
documentation](http://redux.js.org/) for detailed information about the library.
|
|
|
|
|
|
|
|
|
|
![Redux state handling schema](https://github.com/ReCodEx/wiki/raw/master/images/redux.png)
|
|
|
|
|
|
|
|
|
|
The main difference between *Flux* and *redux* is the fact that there is only
|
|
|
|
|
one store with one reducer in redux. The single reducer might be composed from
|
|
|
|
|
several silmple reducers which might be composed from other simple reducers as
|
|
|
|
@ -3495,7 +3497,6 @@ decide which actions it will process and which it will ignore based on the
|
|
|
|
|
*type* of the action. The simple reducers can change only a specific subtree of
|
|
|
|
|
the whole state tree and these subtrees do not overlap.
|
|
|
|
|
|
|
|
|
|
![Redux state handling schema](https://github.com/ReCodEx/wiki/raw/master/images/redux.png)
|
|
|
|
|
|
|
|
|
|
##### Redux Middleware
|
|
|
|
|
|
|
|
|
|