Alchemy React Base Template

This project was bootstrapped with Create React App.

Use this template for all your "from scratch" deliverables. To start, simply run

• npm install
• npm start

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

The Golden Rule:

🦸 🦸‍♂️ Stop starting and start finishing. 🏁

If you work on more than one feature at a time, you are guaranteed to multiply your bugs and your anxiety.

Making a plan in React

1. Make a drawing of your app. Simple "wireframes"
2. Component Tree
   1. Look at the drawing and break it down into Components. Label these Components explicitly (i.e., DogList, etc)
   2. Draw a hierarchy (or tree) of components, describing which components are parents and which are children
   3. Looking at the drawing, make a list of your app's features. What should a user "be able to do" with this app?
   4. Now look at your component tree: which components "go with" which features? Draw lines and make these connections explicitly.
3. State
   1. Look back at the drawing and your list of features and imagine using the app. What state do you need to track?
   2. For each piece of state, ask: "When does it change?" If the answer is, "never", then it is not state.
   3. Similarly, find all the 'events' (user clicks, form submit, on load etc) in your app. Ask one by one, "What state changes?" for each of these events. (This should feel like the the inverse of the previous step.)
   4. Think about how to validate each of your state changes. How will I know if state changed in response to this event? (Hint: react dev tools or console.log usually helps here.)
4. Data flow
   1. Look at your hierarchy and ask: which components need access to which state? Another way to ask this is: for each component, what does this component need to "do its job?". This list becomes the "props" of the component.
   2. If a child needs state from a parent, you will need to pass props. What will you name these props?
   3. Notice especially if two siblings need the same state: if so, you need a callback (i.e., debit card).
5. Pick one feature from your list and build it out. Start with its parentmost component, and work down the component chain. Do not build another feature until this one is finished (and you can prove that it is finished by validating state change).

Additional considerations

• Is any of your state redundant? For example, if you're tracking wins, losses, and total, you can probably get rid of losses state, and calculate it as total - wins.
• Where should each piece of state live? How are you going to get data from where it lives to where it needs to be?