_This is an official bug report that was originally part of the discussion on #4630. That issue was not opened to discuss re-rendering issues with withRouter, whereas this is to discuss issues with the match object not being passed down properly._
[email protected]
[email protected]
http://codepen.io/indiesquidge/pen/KWgoNX
(See codepen link above)
match params should be passed down to components wrapped by withRouter
match params not being passed down to components wrapped by withRouter
It seems like this change was explicitly stating that only the closest <Route>'s match would be available when using withRouter, but it doesn't state that a pathless <Route> will (or should) inherit match from its parent in order to get access to, say, match.params. Should it say that?
Fixed by 394eb09
Most helpful comment
Fixed by 394eb09