From 21b952b6ff582e2c76a050e4203c89b6d2168b16 Mon Sep 17 00:00:00 2001 From: Elizabeth Craig Date: Mon, 4 Mar 2019 15:38:03 -0800 Subject: [PATCH] No more AppTodo --- step1-06/demo/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/step1-06/demo/README.md b/step1-06/demo/README.md index 21cc2ed..4b6b9b8 100644 --- a/step1-06/demo/README.md +++ b/step1-06/demo/README.md @@ -4,7 +4,7 @@ In React, the data travels in one direction: top-down in the form of state propa [Step #3 of "Thinking in React"](https://reactjs.org/docs/thinking-in-react.html) suggests finding the "minimal set of mutable state" that your application requires. So in this demo we are going to add that "minimal state" to our application and drive our UI off of that data. With that done, the next step will be to create ways to modify that state, which will in turn cascade down through our UI. This [reconciliation](https://reactjs.org/docs/reconciliation.html) process, figuring out what in your UI needs to change based on changing state, is what React excels at. -## Adding State to `AppTodo.tsx` +## Adding State to `TodoApp.tsx` Inside our `TodoApp` class, we will add the minimal state for our application, which includes just two keys: `todos` and `filter`. We don't need to worry about a `remaining` value because it can be calculated by counting the number of todos where the `completed` field is set to `false`.