From 58deb56ca1ab2171316f4efd4cde48847157d0e4 Mon Sep 17 00:00:00 2001 From: Michael Chan Date: Mon, 13 Jan 2014 08:27:42 -0800 Subject: [PATCH] Edit thinking-in-react, remove repeated word - removed repeated word 'building' --- blog/2013/11/05/thinking-in-react.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2013/11/05/thinking-in-react.html b/blog/2013/11/05/thinking-in-react.html index 188da3ec7667a..4ba698d2e154c 100644 --- a/blog/2013/11/05/thinking-in-react.html +++ b/blog/2013/11/05/thinking-in-react.html @@ -152,7 +152,7 @@

Start with a mock Step 2: Build a static version in React #

-

Now that you have your component hierarchy it's time to start implementing your app. The easiest way is to build a version that takes your data model and renders the UI but has no interactivity. It's easiest to decouple these processes because building building a static version requires a lot of typing and no thinking, and adding interactivity requires a lot of thinking and not a lot of typing. We'll see why.

+

Now that you have your component hierarchy it's time to start implementing your app. The easiest way is to build a version that takes your data model and renders the UI but has no interactivity. It's easiest to decouple these processes because building a static version requires a lot of typing and no thinking, and adding interactivity requires a lot of thinking and not a lot of typing. We'll see why.

To build a static version of your app that renders your data model you'll want to build components that reuse other components and pass data using props. props are a way of passing data from parent to child. If you're familiar with the concept of state, don't use state at all to build this static version. State is reserved only for interactivity, that is, data that changes over time. Since this is a static version of the app you don't need it.