From 396c6b68ed64e09e991aa08f9e44f99336ca06e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Tue, 7 Apr 2015 13:14:44 -0700 Subject: [PATCH] Merge pull request #3612 from gaearon/patch-1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Mention Flux in “communicate between components” --- docs/tips/14-communicate-between-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tips/14-communicate-between-components.md b/docs/tips/14-communicate-between-components.md index e217340ae8..abd11a169f 100644 --- a/docs/tips/14-communicate-between-components.md +++ b/docs/tips/14-communicate-between-components.md @@ -38,4 +38,4 @@ React.render( Notice the use of `bind(this, arg1, arg2, ...)`: we're simply passing more arguments to `handleClick`. This is not a new React concept; it's just JavaScript. -For communication between two components that don't have a parent-child relationship, you can set up your own global event system. Subscribe to events in `componentDidMount()`, unsubscribe in `componentWillUnmount()`, and call `setState()` when you receive an event. +For communication between two components that don't have a parent-child relationship, you can set up your own global event system. Subscribe to events in `componentDidMount()`, unsubscribe in `componentWillUnmount()`, and call `setState()` when you receive an event. [Flux](https://facebook.github.io/flux/) pattern is one of the possible ways to arrange this.