- Use data to create a web page (Data-driven React)
- Reproduce the Airbnb experiences page with React
- React Framework
- JSX
- Create components from an array
- Mapping data
- Resuable components
- Custom components
- Styling
-
What do props help us accomplish?
Make a component more reusable.
-
How to pass a prop into a component?
<MyAwesomeHeader title="???" />
-
Can pass a custom prop (e.g.
blahblahblah={true}
) to a nativeDOM element? (e.g.
) Why or why not? No, because the JSX we use to describe native DOM elements will be turned into REAL DOM elements by React. And real DOM elements only have the properties/attributes specified in the HTML specification. (Which doesn't include properties likeblahblahblah
) -
How do I receive props in a component?
function Navbar() { return ( <header> ... </header> ) }
Answer:
function Navbar(props) { console.log(props.whatever) return ( <header> ... </header> ) }
-
What data type is
props
when the component receives it?An object
-
What does the
.map()
array method do?Returns a new array. Whatever gets returned from the callback function provided is placed at the same index in the new array. Usually we take the items from the original array and modify them in some way.
-
What do we usually use
.map()
for in React?Convert an array of raw data into an array of JSX elements that can be displayed on the page.
-
Why is using
.map()
better than just creating the components manually by typing them out?It makes our code more "self-sustaining" - not requiring additional changes whenever the data changes.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
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 for more information.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify