Skip to content

Commit

Permalink
SRS 4: Added exercises, fixed writeup
Browse files Browse the repository at this point in the history
  • Loading branch information
matthewcn56 committed Jul 22, 2021
1 parent e720ec7 commit 745dc52
Show file tree
Hide file tree
Showing 24 changed files with 12,214 additions and 26 deletions.
52 changes: 26 additions & 26 deletions supplemental-react/04_accustomed_to_custom_hooks/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,19 +15,19 @@ This week, we'll talk about how custom hooks embody all of these concepts and **
- [Hooked Components Handling State Logic](#hooked-components-handling-state-logic)
- [Discrete Logic](#discrete-logic)
- [Custom Hooks](#custom-hooks)
- [Why Use Custom Hooks?](#why-use-custom-hooks?)
- [Why Use Custom Hooks?](#why-use-custom-hooks)
- [Custom Hooks Vs React Context](#custom-hooks-vs-react-context)
- [Custom Hooks Can Improve React App Performance](#custom-hooks-can-improve-react-app-performance)
- [Custom Hook Performance](#custom-hook-performance)
- [Context Performance](#context-performance)
- [Prop Drilling Performance](#prop-drilling-performance)
- [Example useWindowDimensions Custom Hook](#example-usewindowdimensions-custom-hook)
- [How Do Custom Hooks Solve Common Problems?](#how-do-custom-hooks-solve-common-problems?)
- [How Do Custom Hooks Work?](#how-do-custom-hooks-work?)
- [How Do Custom Hooks Solve Common Problems?](#how-do-custom-hooks-solve-common-problems)
- [How Do Custom Hooks Work?](#how-do-custom-hooks-work)
- [Functional Composition](#functional-composition)
- [Making Custom Hooks](#making-custom-hooks)
- [Creating Our Custom Hook Functions](#creating-our-custom-hook-functions)
- [Using Custom Hooks](#using-custom-hooks)
- [Custom Hooks Can Improve React App Performance](#custom-hooks-can-improve-react-app-performance)
- [Custom Hook Performance](#custom-hook-performance)
- [Context Performance](#context-performance)
- [Prop Drilling Performance](#prop-drilling-performance)
- [Custom Hooks Use Case](#custom-hooks-use-case)
- [Conclusion](#conclusion)

Expand Down Expand Up @@ -128,6 +128,24 @@ Besides from using custom hooks, how can we implement this functionality?

![drillingPic](https://github.com/uclaacm/teach-la-dev-training/blob/main/archive/s21/advanced_react_track/04_global_state_of_mind/pictures/propDrilling.png)

## Custom Hooks Can Improve React App Performance

By using the [React Developer Tools Chrome Extension](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi/related?hl=en) we can "profile" our React apps for performance and see how many times our components have to re-render!

Let's take a look and compare the performance of each of the three approaches: custom hooks, context, and prop drilling, and compare how many times the "parent component" is forced to re-render even if it doesn't care about logic that only its children component use.

### Custom Hook Performance

![customPerf](./pictures/customHookProfiler.png)

### Context Performance

![contextPerf](./pictures/contextProfiler.png)

### Prop-Drilling Performance

![drillingPerf](./pictures/drillingProfiler.png)

# How Do Custom Hooks Solve Common Problems?

Performance problems of wrapping entire component trees with React Contextare solved because you only need to call the custom hook inside the components that depend on its logic.
Expand Down Expand Up @@ -168,7 +186,7 @@ In this example of functional composition, you can simply call a child function

Custom hooks do the exact same thing! If two components share logic that can be encapsulated into a separate component, you can create a **custom hook** that can be called multiple times within different React components.

![encapsulationDigraph](./pictures/encapsulation)
![encapsulationDigraph](./pictures/logicDependency.png)

To determine if logic can be encapsulated into a separate component, take a look at what other logic it depends on. Looking at this digraph for instance, since 1,2,3 depend on each other, that logic can be encapsulated and likewise for 4,5.

Expand Down Expand Up @@ -262,24 +280,6 @@ function SonComponent() {

As you can see, we don't need to use state **at all** within our component itself, but it updates as our window changes since all the state/effect logic is encapsulated within our custom hook.

## Custom Hooks Can Improve React App Performance

By using the [React Developer Tools Chrome Extension](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi/related?hl=en) we can "profile" our React apps for performance and see how many times our components have to re-render!

Let's take a look and compare the performance of each of the three approaches: custom hooks, context, and prop drilling, and compare how many times the "parent component" is forced to re-render even if it doesn't care about logic that only its children component use.

### Custom Hook Performance

![customPerf](./pictures/customHookProfiler.png)

### Context Performance

![contextPerf](./pictures/contextProfiler.png)

### Prop-Drilling Performance

![drillingPerf](./pictures/drillingProfiler.png)

## Custom Hooks Use Case

Custom hooks are another tool that we can add to our toolkit of ways to organize React code and write better, cleaner, and more efficient code!
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.

# dependencies
/node_modules
/.pnp
.pnp.js

# testing
/coverage

# production
/build

# misc
.DS_Store
.env.local
.env.development.local
.env.test.local
.env.production.local

npm-debug.log*
yarn-debug.log*
yarn-error.log*
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `yarn start`

Runs the app in the development mode.\
Open [http://localhost:3000](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.

### `yarn test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `yarn build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `yarn eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

## Learn More

You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).

To learn React, check out the [React documentation](https://reactjs.org/).
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
{
"name": "exercises",
"version": "0.1.0",
"private": true,
"dependencies": {
"@testing-library/jest-dom": "^5.11.4",
"@testing-library/react": "^11.1.0",
"@testing-library/user-event": "^12.1.10",
"@types/jest": "^26.0.15",
"@types/node": "^12.0.0",
"@types/react": "^17.0.0",
"@types/react-dom": "^17.0.0",
"@types/react-router-dom": "^5.1.8",
"react": "^17.0.2",
"react-dom": "^17.0.2",
"react-router-dom": "^5.2.0",
"react-scripts": "4.0.3",
"typescript": "^4.1.2",
"web-vitals": "^1.0.1"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
Binary file not shown.
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<link rel="icon" href="%PUBLIC_URL%/favicon.ico" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta name="theme-color" content="#000000" />
<meta
name="description"
content="Web site created using create-react-app"
/>
<link rel="apple-touch-icon" href="%PUBLIC_URL%/logo192.png" />
<!--
manifest.json provides metadata used when your web app is installed on a
user's mobile device or desktop. See https://developers.google.com/web/fundamentals/web-app-manifest/
-->
<link rel="manifest" href="%PUBLIC_URL%/manifest.json" />
<!--
Notice the use of %PUBLIC_URL% in the tags above.
It will be replaced with the URL of the `public` folder during the build.
Only files inside the `public` folder can be referenced from the HTML.
Unlike "/favicon.ico" or "favicon.ico", "%PUBLIC_URL%/favicon.ico" will
work correctly both with client-side routing and a non-root public URL.
Learn how to configure a non-root public URL by running `npm run build`.
-->
<title>React App</title>
</head>
<body>
<noscript>You need to enable JavaScript to run this app.</noscript>
<div id="root"></div>
<!--
This HTML file is a template.
If you open it directly in the browser, you will see an empty page.
You can add webfonts, meta tags, or analytics to this file.
The build step will place the bundled scripts into the <body> tag.
To begin the development, run `npm start` or `yarn start`.
To create a production bundle, use `npm run build` or `yarn build`.
-->
</body>
</html>
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
{
"short_name": "React App",
"name": "Create React App Sample",
"icons": [
{
"src": "favicon.ico",
"sizes": "64x64 32x32 24x24 16x16",
"type": "image/x-icon"
},
{
"src": "logo192.png",
"type": "image/png",
"sizes": "192x192"
},
{
"src": "logo512.png",
"type": "image/png",
"sizes": "512x512"
}
],
"start_url": ".",
"display": "standalone",
"theme_color": "#000000",
"background_color": "#ffffff"
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# https://www.robotstxt.org/robotstxt.html
User-agent: *
Disallow:
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
.App {
text-align: center;
}

.content-container {
background-color: #bebebe;
min-height: 100vh;
display: flex;
flex-direction: column;
align-items: center;
justify-content: flex-start;
font-size: calc(10px + 4vmin);
}

.subcomponent-container {
padding: 2vw;
background-color: #ebebeb;
}

.todo-container {
background-color: rgb(197, 255, 130);
margin: 2vw;
padding: 2vw;
}

.odd-component {
background-color: rgb(197, 255, 130);
margin: 2vw;
padding: 2vw;
}

.even-component {
background-color: #bebebe;
margin: 2vw;
padding: 2vw;
}

.button-container {
font-size: calc(10px + 2vmin);
margin: 5px;
}

.active-button {
background-color: rgb(197, 255, 130);
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
import React from "react";
import { BrowserRouter as Router, Switch, Route, Link } from "react-router-dom";
import ContextPage from "./pages/ContextPage";
import CustomHookPage from "./pages/CustomHookPage";
import PropDrillingPage from "./pages/PropDrillingPage";

import "./App.css";

function App() {
return (
<Router>
<div className="App">
<div className="content-container">
<nav>
<div>
<Link to="/custom">
<button className="button-container">Custom Hooks</button>
</Link>

<Link to="/context">
<button className="button-container">useContext</button>
</Link>
<Link to="/drilling">
<button className="button-container">Prop Drilling</button>
</Link>
</div>
</nav>

<Switch>
<Route exact path="/">
Click a page on the top to get started!
</Route>

<Route path="/custom">
<div className="subcomponent-container">
<CustomHookPage />
</div>
</Route>
<Route path="/context">
<div className="subcomponent-container">
<ContextPage />
</div>
</Route>
<Route path="/drilling">
<div className="subcomponent-container">
<PropDrillingPage />
</div>
</Route>
</Switch>
</div>
</div>
</Router>
);
}

export default App;
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
body {
margin: 0;
font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', 'Roboto', 'Oxygen',
'Ubuntu', 'Cantarell', 'Fira Sans', 'Droid Sans', 'Helvetica Neue',
sans-serif;
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale;
}

code {
font-family: source-code-pro, Menlo, Monaco, Consolas, 'Courier New',
monospace;
}
Loading

0 comments on commit 745dc52

Please sign in to comment.