From 21d91e6f5fcea0fecc2e9414fffcfd18505e5d37 Mon Sep 17 00:00:00 2001 From: Dan Abramov Date: Tue, 7 Apr 2015 19:44:20 +0300 Subject: [PATCH] =?UTF-8?q?Mention=20Flux=20in=20=E2=80=9Ccommunicate=20be?= =?UTF-8?q?tween=20components=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 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.