React Router Prework.md

React Router Prework

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.

Instructions

1. Fork this gist
2. On your own copy, go through the listed readings and answer associated questions
3. Comment a link to your forked copy on the original gist

Questions / Readings

Router Overview

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:

1. 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)

2. What package do we need to install to use React Router?

• react-router-dom

Router Components

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

Routers

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.

3. What is a <BrowserRouter />?

• A that uses the HTML5 history API (pushState, replaceState and the popstate event) to keep your UI in sync with the URL.

4. Why would we use <BrowserRouter /> in our apps?

• So that we can control the path of the URL, and help a user understand where in the web application they currently are.

Route Matchers

5. What does the <Route /> component do?

• Render some UI when its path matches the current URL.

6. How does the <Route /> component check whether it should render something?

• By checking the path attribute that has been assigned to the component, and see which one matches the current URL, and it will then display the components that are children of the matching path inside of the that route.

7. What does the <Switch /> component do?

• Renders the first child or that matches the location

8. How does it decide what to render?

• Searches through its children elements to find one whose path matches the current URL. When it finds one, it renders that and ignores all others.

Route Changers

9. What does the <Link /> component do? How does a user interact with it?

• Provides declarative, accessible navigation around your application. User interacts with it by clicking it.

10. What does the <NavLink /> component do? How does a user interact with it?

• A special version of the that will add styling attributes to the rendered element when it matches the current URL. User interacts with it by clicking it.

11. What does the <Redirect /> component do?

• Rendering a will navigate to a new location. The new location will override the current location in the history stack.