Resource IDs in routes

One common use case is to make the ID of a resource part of the URL. This makes it easy for your code to get the ID, then make an API call that fetches the relevant resource data. Let's implement a route that renders a user detail page. This will require a route that includes the user ID, which then needs to somehow be passed to the component so that it can fetch the user.

Let's start with the App component that declares the routes:

import React, { Fragment } from "react";
import { BrowserRouter as Router, Route } from "react-router-dom";
import UsersContainer from "./UsersContainer";
import UserContainer from "./UserContainer";

export default function App() {
  return (
    <Router>
      <Fragment>
        <Route exact path="/" component={UsersContainer} />
        <Route path="/users/:id" component={UserContainer} />
      </Fragment>
    </Router>
  );
} 

The...