Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript React Router 4 Basics Navigating, Nesting and Redirecting Routes Using the Match Object

Posted by Mike Straw
Mike Straw
7,100 Points

Why do we need `match.url` in the NavLink components?

Is there a particular reason to add the ${match.url}/ to the path in the NavLinks? It works just fine using a relative path, as well:

      <ul className="course-nav">
        <li><NavLink to='html'>HTML</NavLink></li>
        <li><NavLink to='css'>CSS</NavLink></li>
        <li><NavLink to='javascript'>JavaScript</NavLink></li>
      </ul>

It makes sense to use the match.path in the routes since those are needed to make it work, but on the NavLinks it seems like extra code and work that serves no real purpose.