Skip to content

Commit 9f5403b

Browse files
committed
Include image
1 parent 10bcfdf commit 9f5403b

File tree

2 files changed

+2
-0
lines changed

2 files changed

+2
-0
lines changed

docs/_posts/2014-07-30-flux-actions-and-the-dispatcher.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ Different actions are identified by a type attribute. When all of the stores rec
2424

2525
Letting the stores update themselves eliminates many entanglements typically found in MVC applications, where cascading updates between models can lead to unstable state and make accurate testing very difficult. The objects within a Flux application are highly decoupled, and adhere very strongly to the [Law of Demeter](http://en.wikipedia.org/wiki/Law_of_Demeter), the principle that each object within a system should know as little as possible about the other objects in the system. This results in software that is more maintainable, adaptable, testable, and easier for new engineering team members to understand.
2626

27+
<img src="/react/img/blog/flux-diagram.png" style="width: 100%;" />
28+
2729

2830
Why We Need a Dispatcher
2931
------------------------

docs/img/blog/flux-diagram.png

177 KB
Loading

0 commit comments

Comments
 (0)