This gist contains a short assignment I'd like everyone to complete before our formal lesson. The prework involves reading some of the React Router documentation, and will allow us to keep the lesson more hands on.
- Fork this gist
- On your own copy, go through the listed readings and answer associated questions
- Comment a link to your forked copy on the original gist
React Router is a library that allows us to make our single page React applications mimic the behavior of multipage apps. It provides the ability to use browser history, allowing users to navigate with forward / back buttons and bookmark links to specific views of the app. Most modern sites use some form of routing. React Router exposes this functionality through a series of components. Let's start by looking at the overall structure of an app using router:
-
Take a look at the quick start page of the React Router docs. Take note of the syntax and organization of the page. No worries if this looks unclear right now! (nothing to answer here)
-
What package do we need to install to use React Router? react-router-dom
React Router provides a series of helpful components that allow our apps to use routing. These can be split into roughly 3 categories:
- Routers
- Route Matcher
- Route Changers
Any code that uses a React-Router-provided component must be wrapped in a router component. There are lots of router components we can use, but we'll focus on one in particular. Let's look into the docs to learn more.
-
What is a
<BrowserRouter />
? It uses that uses the HTML 5 history API that makes the URL reflect the UI. -
Why would we use
<BrowserRouter />
in our apps? it keeps UI in sync with the UI, and to easily control navigation around our applications.
-
What does the
<Route />
component do? it matches the Ui with the associated url -
How does the
<Route />
component check whether it should render something? it renders the matched components that have a path of the current url -
What does the
<Switch />
component do? it renders the first child route or redirects to the matched url -
How does it decide what to render? it looks at the route path that matches the url
-
What does the
<Link />
component do? How does a user interact with it? it allows for user interaction and basically is a hyperlink tot he url -
What does the
<NavLink />
component do? How does a user interact with it? it is a hyperlink that takes the user to the associated page on click -
What does the
<Redirect />
component do? taeks a user to tha new location and gets rid of the current area the user is looking at.