Tutorial

Mapping Routes in React Router

Published on June 23, 2017
author

Matthew Garcia

Mapping Routes in React Router

While we believe that this content benefits our community, we have not yet thoroughly reviewed it. If you have any suggestions for improvements, please let us know by clicking the “report an issue“ button at the bottom of the tutorial.

In some cases, it may be beneficial to store routes as objects instead of components.

The problem

In larger applications, routes quickly get repetitive, verbose, and repetitive. 😉

// App.js
class App extends Component {
  render() {
    return (
      <BrowserRouter>
        <div>
          <Route exact path="/" component={HomePage} />
          <Route exact path="/Teachers" component={TeacherListPage} />
          <Route exact path="/Teachers/:teacherId" component={TeacherPage} />
          <Route exact path="/Teachers/:teacherId/Classes" component={TaughtClassesPage} />
        {/* And on and on for classes, grades, students, et cetera. */}
        </div>
      </BrowserRouter>
    );
  }
}

It’s a huge brick of text in the middle of your render. It works, but it doesn’t look too good. Previous versions of React Router represented routes as objects; while that syntax is gone with React Router 4, it’s pretty easy to throw together something similar.

Representing Routes as Objects

You probably noticed that routes tend to take the same kind of props. Let’s represent them as objects:

// You can declare this in `App.js`, but it might
// be better to move it to its own file.

const routes = [{
  path: '/',
  component: HomePage,
}, {
  path: '/Teachers',
  component: TeacherListPage,
}, {
  path: '/Teachers/:teacherId',
  component: TeacherPage,
}, {
  path: '/Teachers/:teacherId/Classes',
  component: TaughtClassesPage,
}, /* And so on. */];

Using this object, you can simplify App:

class App extends Component {
  render() {
    const routeComponents = routes.map(({path, component}, key) => <Route exact path={path} component={component} key={key} />);
    return (
      <BrowserRouter>
        {routeComponents}
        </div>
      </BrowserRouter>
    );
  }
}

Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.

Learn more about us


About the authors
Default avatar
Matthew Garcia

author

Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?
 
Leave a comment


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Join the Tech Talk
Success! Thank you! Please check your email for further details.

Please complete your information!

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel