It's not really bananas when you actually start to think of everything 'as components', and consider that 'render' can neatly, declaratively describe behaviour, not just the DOM.
Usually when I need to trigger a redirect, I'm in some business-level function. So to redirect this way, I would need to set some state in my store, re-render, then hit the conditional, which would redirect, probably unset that state, and then probably trigger some additional business logic.
When really all I want to do is in the business function, directly trigger the redirect and maybe some other logic without any indirection. redux-react-router exists, but it's API is still obtuse compared to something like redux-first-router.
Heh, didn't see this comment before I left a novel up the tree. Seems we have similar ideas about state management.
I think the default RR API is straight React, and that is by design.
I somewhat agree that the <Redirect /> component is not actually that useful, it's only useful in very simple cases like "based on one route plus conditional redirect to another", e.g.:
<Route path="/">
{usersPreviousShoppingGender === "women" ? (
<Redirect to="/women" />
) : (
...
)}
...
</Route>
<Route path="/women">You're not using React to its full potential if you think like this.