Lab: LotR
Last updated
Last updated
Let's build something small to reinforce what you've learned so far. We're going to practice creating components and passing information into them.
We'll build a simple website that shows title and runtime information about the original Lord of the Rings Trilogy
.
Specifically, at the end of this lesson, your solution will look like this:
Fork and clone this repo.
Open up your ./src
directory in your favorite text editor.
Inside of ./src
folder, create a new React Component file called Movie.js
.
src/Movie.js
or, we could write it as a functional component, like so:
Let's add some JSX to this component will be visible in our application. Let's keep the JSX simple for now, and we'll make it more complex once we're sure it works.
Remember, our goal is to display the movie title and runtime information.
Let's add one <h1>
for the movie title, and a <p>
for the runtime. Remember, the JSX of each component in React ultimately must descend from just one parent element. Wrap the <h1>
and <p>
in a <div>
.
The JSX will look like this:
Add this JSX to the component so that it's returned.
src/Movie.js
Let's make this component appear on the page. One great thing about using create-react-app
is it tells us exactly what we need to do to start editing our application. The homepage says, "To get started, edit src/App.js
and save to reload." Let's do that!
Open src/App.js
.
Add our <Movie />
component inside of the App
component. Go back to Chrome browser
and see if it appears.
Uh oh. There's an error.
'Movie'
is not defined? Ah.
One does not simply refer to components in React. In our src/App.js
, we're saying "Display what's returned from the Movie
component." However - we haven't told src/Apps.js
where to find the Movie
component! We must import a component before using it.
Add this import statement with the other imports at the top of the src/App.js
file.
Now you should see the page without the error message, and it should have the JSX from the Movie component.
The entire App.js
should look like this:
src/App.js
We need to make our Movie component accept information so we can use it to display different titles and runtimes. In the src/App.js
file, add title
, hours
, and minutes
props to the <Movie />
tag. We'll be able to read the value of these props from inside the component. You can name props pretty much anything you want - but it's good practice to be descriptive!
We'll be able to read the value of these props
from inside the component. You can name props pretty much anything you want - but it's good practice to be descriptive!
React gathers all of the props we added to the call to <Movie />
and makes them each available through the props
object. This means that inside the Movie
component, we can now access the values of props through props.title
, this.props.hours
and props.minutes
. Remember, we use curly braces { }
to display the value of something.
In src/Movie.js
, change the <h1>
to display the value of the title
prop by writing {props.title}
.
There was also the hours
and minutes
props. Update the JSX to access and display the value of each prop we created.
The render()
function ends up looking like this:
src/Movie.js
Refresh the page and make sure everything works correctly.
Once you've got props working for one component, then write two more!
In src/App.js
, call the <Movie />
component again with different values for the title
, hours
and minutes
properties. Display information for the complete trilogy! (If you don't know everything about Lord of the Rings off the top of your head, here it is).
When you're finished, review the reflections below.
Components are great because they allow us to compartmentalize code and easily reuse parts we create. We simply set the value of props
and the component defines how everything should be displayed.
In this instance, we factored out some redundancy of the movie titles.
All these movies start with "Lord of the Rings:"
, so only the unique part is the prop.
Similarly, we don't have to rewrite the format of the runtime information.
Building and reusing components becomes especially powerful the more complex components become.
Imagine building a component for video search results inside YouTube.
The props
object is huge:
ton of links
time information
preview images
options to add the result to a playlist
and all sorts of other things.
Building one component to rule all them all would save you a lot of time and headaches!
props
.In case you want to nerd out, here are handy links to the IMDB page for each movie:
array
of objects
with all of LOTR
movies and properties.screenshot
in SlackGithub