withRouter HOC

[jonaskello]

withRoute HOC Will create a new component, injecting your router instance (from context) and the current route to the > > wrapped component. Any route change will trigger a re-render.

I think it could be useful to have a HOC that only injects the router that can be used in cases where you just want the router but are getting the route from Redux. Basically it would just inject the router from the context as a prop.

[troch]

Hi @jonaskello, this repo has been moved to the main router5 repo. A withRouter HOC can easily be added

[jonaskello]

Aha, ok I might re-post there. I'm not sure it is needed however. I was under the impression you needed the router in order to navigate but I I found that I can use the navigate action instead when using the redux integration. Might still be interesting when you don't use redux integration though.

[troch]

There are Link and BaseLink components available.

You can also create your own link component to navigate.You don't have to use a HOC to inject your router instance, you can define contextTypes directly.

class Link extends PureComponent {
    constructor(props, context) {
        super(props, context)
        this.router = context.router
    }

    render() {
        /* ... */
    }
}

Link.contextTypes = {
    router: PropTypes.object.isRequired
}

[troch]

• Link is BaseLink with the withRoute HoC (which requires the listener plugin)
• BaseLink isn't bound to route changes, so is best if you don't need to change your link appearance when the route it links to is active, or if you use redux and you want to bind to your store yourself.

[jonaskello]

Yes, I basically did a HOC that injected the router from the context. I use typescript and AFAIK contextTypes is not possible to type, so to use context I need to go through some tricks like casting to the component to any etc. Also you need to import the prop-types package in all components that use context. So basically it is just a convenience HOC to inject the router from context without going through the troubles of specifying contextTypes directly in the component.

But as you say I think for redux it is better to just use the store for everything.