react-router-config does not match on later paths even if there is an exact path match later

Version

4.1.1

Test Case

None

Steps to reproduce

Create a react-router-config that has the following:

    [{ component: someAuthorizedLayout
        routes: [
            {component: AuthorizedDashboard, path: '/home, exact: true}
       ]
     },
     { component: UnauthorizedLayout
         routes: [
            {component: Login, path: '/', exact: true}
        ]
     }]

Try to go to ‘/’ and you are unable to. Why? Because the route matches the first route and “consumes” the request before it realizes that there is a ‘/’ exact match

Expected Behavior

I expect it to go to the Login page.

Actual Behavior

It goes to no route because it traverses the routes tree and when it hits someAuthorizedLayout it finds no nested routes that match.

Is this a bug? or is this by design?

[timdorr]

This does appear to be a bug in rrc. We’re not doing any testing of that form of routes, so the first step would be to add a failing test. Then we can go about fixing for it.

Edit: Why are people thumbs-downing me? 😭

[mjackson]

I believe renderRoutes should not be using a <Switch> internally, but rather should return an array of <Route> elements.