From 031d8c442c11a754aabb9a7c9c2bd5a400d62c15 Mon Sep 17 00:00:00 2001 From: dschafer Date: Tue, 29 Apr 2014 19:53:13 -0700 Subject: [PATCH] Update jsfiddles in thinking-in-react to remove onSubmit from forms --- docs/thinking-in-react.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/thinking-in-react.md b/docs/thinking-in-react.md index 77b40a8c..c8f1ac16 100644 --- a/docs/thinking-in-react.md +++ b/docs/thinking-in-react.md @@ -61,7 +61,7 @@ Now that we've identified the components in our mock, let's arrange them into a ## 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 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. @@ -105,7 +105,7 @@ So finally, our state is: ## Step 4: Identify where your state should live - + 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. @@ -130,7 +130,7 @@ You can start seeing how your application will behave: set `filterText` to `"bal ## Step 5: Add inverse data flow - + 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`.