Ability to unsubscribe from hashHistory.listen()

While trying to find the best solution for creating my own breadcrumb, I found it difficult to get route information into a sibling component in my case a navigation bar.

As of right now i’m using the hashHistory.listen() method and splitting the response using event.pathname.split("/"). This method works but since i’m using an event listener i receive an error if i navigate to a new route that doesn’t contain my component. This the the expected behavior which leads me to think that there should be an unlisten() method to hashHistory.

Another plus would be to have both parent and child routes listed in the hashHistory.listen() response. This would help tremendously in know the exact components used to render parameters.

[timdorr]

First, the return from history.listen() is an “unlisten” function you can call.

But you’re provided the location on your route component. Pass that down via props to your breadcrumb component if you need it deeper in the tree.

[edgeadjei]

After further research i finally understand what you were both trying to convey. I couldn’t wrap my mind around how a parent component would know a child component’s route without re-rendering. but for anybody looking to accomplish the same task you can get all active routes in a child component by passing routes={this.props.routes} to the component and access the current route object using routes[routes.length -1]

Thank you both. React router is awesome.