Update jsfiddles in thinking-in-react to remove onSubmit from forms
dschafer committed
Apr 29, 2014 at 19:53 UTC
fbbace6b6925f48bd1f377e153a929cbc604a0de
1 file changed
+3
-3
docs/docs/thinking-in-react.md
+3
-3
@@ -61,7 +61,7 @@ Now that we've identified the components in our mock, let's arrange them into a
61
62
## Step 2: Build a static version in React
63
64
-<iframe width="100%" height="300" src="http://jsfiddle.net/6wQMG/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
64
+<iframe width="100%" height="300" src="http://jsfiddle.net/n25pd/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
65
66
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.
67
@@ -105,7 +105,7 @@ So finally, our state is:
105
106
## Step 4: Identify where your state should live
107
108
-<iframe width="100%" height="300" src="http://jsfiddle.net/QvHnx/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
108
+<iframe width="100%" height="300" src="http://jsfiddle.net/t53sx/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
109
110
OK, so we've identified what the minimal set of app state is. Next we need to identify which component mutates, or *owns*, this state.
111
@@ -130,7 +130,7 @@ You can start seeing how your application will behave: set `filterText` to `"bal
130
131
## Step 5: Add inverse data flow
132
133
-<iframe width="100%" height="300" src="http://jsfiddle.net/3Vs3Q/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
133
+<iframe width="100%" height="300" src="http://jsfiddle.net/F8H7p/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
134
135
So far we've built an app that renders correctly as a function of props and state flowing down the hierarchy. Now it's time to support data flowing the other way: the form components deep in the hierarchy need to update the state in `FilterableProductTable`.
136