- Avoid derived state
Shouldn't copy props into state - check examples/challenges - form ones in particular. See: https://reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html
- More React Router information
- Hash router for deployment
- Routes inside non-App components
- Add file locations
- Where stuff goes in component
- JSX in render
- State manipulation in handler methods
- Setup state in constructor
- this.props available everywhere
- this.state available everywhere
- Diagram explaining classes
- Show methods being inside class but not each other
- Show scope of
this - Show that
this.propsandthis.stateare available anywhere in the class
- Add more info about
exactpath in ReactRouter - Add more info about setState() ordering
- More lifecycle challenges
- A bit more about what a Component actually is - creates a class, when used creates an instance
- Rewrite Lifting State notes - folks still a bit confused by it all
Just have the buttons material - get rid of the Form stuff
- Diagram
- Notes on how we get what looks like two way flow
- Rename props to
handleClickinstead ofonClick - List of steps for lifting state
- Use function version of
setStatein notes/examplesShould use
setStateas a function to avoid any asynchronous rendering issues- Notes
- Challenge Answers
- Blog Form code?
- Class properties
- Add a few more tests to the ToDo reducers
- useEffect Challenges
Do Week 9 Lifecycle Challenges first
- Custom hooks challenges
- Cover
useCallback? - Cover testing components?
- Update to using
<>instead ofReact.Fragment - Update answers/example to use handleX instead of onX when passing around functions
- For state have some challenges that just turn stateless into stateful components - maybe some more simple challenges
- Deployment Guide
- Make sure basic hooks challenge includes some controlled components
initial->initialState- API challenges need more explaining
- Update to use Bootstrap 4
- Switch to
.jsinstead of.jsx- Challanges
- Notes
- Scripts