Skip to content

Commit 1f14ff1

Browse files
author
Vlad Balin
committed
Update readme.md
1 parent cd4b569 commit 1f14ff1

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

examples/todomvc/readme.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,12 @@ It's works faster than any generic PureRenderMixin because we dynamically compil
6565

6666
Why it's better than just deal with immutable data? Because we can have circular references, and premanent references to objects in data layer with no problems. Thus, you may safely pass nested models and collection around. As you most likely used to.
6767

68+
### But how unidirectional data flow can work?
69+
70+
Because our models and collections can be nested, and parents detects nested changes. So, when you put something complex to the top-level component state, the state (which itself is the model in our case) will notice any changes happend deep inside, and triggers UI update.
71+
72+
There's another example illustrating that, which is a bit simpler - [flux-comparison](https://github.com/Volicon/NestedReact/tree/master/examples/flux-comparison).
73+
6874
### What does `editing : ToDo.from( '^props.todos' )` from `todolist.jsx` mean?
6975

7076
This is NestedTypes type annotation, which literally means "`editing` is the model of `ToDo` type which is taken from

0 commit comments

Comments
 (0)