React-router @@router/LOCATION_CHANGE available in subcomponents Updaters

[jmarceli]

React-router @@router/LOCATION_CHANGE available in subcomponents Updaters

[eliperelman]

Also of use is the pattern laid out in redux-boilerplate by using onEnter to emit a URL change action. Doesn't cover all use cases but maybe a good majority.

[tomkis]

Interesting, I was also thinking about such a feature earlier. @slorber was also thinking about something similar (slorber/scalable-frontend-with-elm-or-redux#2).

Anyway for your specific usecase, it does make sense to dispatch an action in componentWillReceiveProps when your router params change (it's pretty common actually in react-router world).

[jmarceli]

Thanks for replies.
@tomkis1 Your solution works well in my case. Example below (for future reference):

class OrderPage extends React.Component {
  componentWillReceiveProps(nextProps) {
    if (this.props.params.id !== nextProps.params.id) {
      // this will be dispatched each time the route is changed from `orders/1` to `orders/2` 
      this.props.dispatch({ type: action.Load, orderId: nextProps.params.id });
    }
  }
  render() { ... }
}
export default view(({ model, dispatch, params }) => (
  <OrderPage dispatch={dispatch} model={model} params={params} />
));

@eliperelman onEnter is nice alternative but I'm afraid that in my case it would be hard to track down all "routing" buttons and add onEnter to all of them (high probability of runtime bugs).

Anyway @tomkis1 how do you feel about idea of "global" action prefixes. I know that they should not exists in perfectly fractal (Elm) world but for ensuring compatibility with standard react/redux libraries they might be useful.

[tomkis]

@jmarceli I think it's something we can totally consider adding as part of the framework. However, need to figure out proper API. So far having an option to configure "global actions" seems the most sane to me.