- Use
createBrowserRouter
to create a client-side router. - Use
RouterProvider
to include the router in your app. - Use the
<NavBar>
component to allow client-side navigation. - Use
errorElement
to set up router error handling.
In this lab we are going to build out a Movie application that has routes for a Home Page, Actors Page, Movie Page, and Directors Page. Our goal is to provide routes and links for these 4 pages.
Let's work through this one component at a time.
Our src
folder contains the following JavaScript files:
src/
├── data.js
├── index.js
├── routes.js
├── components/
├── MovieCard.js
├── NavBar.js
└── pages/
├── Actors.js
├── Directors.js
├── Home.js
├── Movie.js
You'll need to fill out these various files to get your app up and running. You're free to make new components when you feel that doing so is warranted.
You'll be adding the routes you create to this file and saving them within the
routes
variable. You'll need to provide routes for /
, /directors
,
/actors
, and /movie
. The /movie
route should also include a URL parameter
called title
. Don't forget that you'll need to import components into this
file!
Our index.js
file is currently broken. (It's not rendering anything!) You'll
need to update it to provide routing to our application using
createBrowserRouter
and RouterProvider
.
This file contains seed data for Actors, Movies, and Directors.
This component needs to render three NavLink
components. They will be for /
,
/directors
, and /actors
, in this order (test checks for this). The NavLink
for /
should render Home
, directors
should render Directors
, and
actors
should render Actors
. Each page should render the NavBar.
This component is already set up to render the title of one movie. You'll need
to pass it the appropriate props to render a movie's title. You'll also need to
use a Link
component from react-router-dom
that uses dynamic routing to link
a user to the Movie
page, using the movie title as a parameter.
Note: The titles of the movies contain empty spaces, which are translated into
%20
when injected into the URL of a webpage. This is known asURL Encoding
. URL Encoding takes characters that are not valid URL characters and translates them into a valid character couterpart. All empty spaces are encoded to%20
, for example.react-router-dom
takes care of encoding our URLs for us, and de-encoding them when we access URL parameters viauseParams
. Pretty cool!
This component should render on the /
route. It should display the text Home Page
in an <h1>
. It should also render a list of movies using MovieCard
components.
This component should render on the /movie
route. You will need to include a
URL parameter of title
on that route.
The component will display information about one specific movie. It should
display the movie's title in an <h1>
tag, the movie's time in a <p>
tag, and
each of the movie's genres within its own <span>
tag.
You'll need to use the useParams
hook to get URL parameter data about which
movie you want to render, then use that data to render the appropriate movie.
This component should render on the /directors
route. It should display the
text Directors Page
in an <h1>
, and render a new <article>
element for
each director in our array of directors. The <article>
should contain the
director's name in an <h2>
and a <ul>
with a list of their movies.
This component should render the text Actors Page
in an <h1>
, and render a
new <article>
element for each actor in our array of actors. The <article>
should contain the actor's name in an <h2>
and a <ul>
with a list of their
movies.
Note: The tests will count how many
<article>
s are nested inside yourDirectors
andActors
components. So to get tests to pass, you must create exactly one<article>
for each director or actor, and no additional nested<article>
s in those components.
You'll need to create a new component within the pages
folder for our
ErrorPage
. This page should display our NavBar
component, along with the
text "Oops! Looks like something went wrong." in an <h1>
.
Note: Even when all of your tests are passing, you will see a
console.warn
message indicating that the route the test file is using —bad-route
— doesn't match any routes.