Replayed actions not passed through middleware when using redux-devtools-extension

Hello, I’m trying to adopt use of redux-devtools-extension in my project but I’ve encountered the error from title . Would appreciate some help with the issue if possible.

I’m using Redux DevTools extension 2.11.1

along with:

redux@3.3.0
ng-redux@3.3.3

When I dispatch actions through store.liftedStore.dispatch they aren’t going through my redux middlewares stack(defined in my application as middlewares). Obviously when I run actions through store.dispatch everything works correctly.

The same applies when using slider in redux-devtools-extension - my middleware chain doesn’t receive replayed actions.

I couldn’t find solution on https://github.com/zalmoxisus/redux-devtools-extension/blob/master/docs/Troubleshooting.md

redux-devtools-extension is the only enhancer that I’m using, but maybe ngRedux applies it wrong? I’m initializing store this way:

$ngReduxProvider.createStoreWith(
  rootReducer, 
  middlewares,
  [window.__REDUX_DEVTOOLS_EXTENSION__()])

You can see how final store is composed under this link: https://github.com/angular-redux/ng-redux/blob/3.3.0/src/components/ngRedux.js#L16

Maybe it has something to do with https://github.com/reactjs/redux/issues/1051 ? I’m trying to figure it out on my own but would appreciate some help.

[zalmoxisus]

@Machiaweliczny, what if we’d pass the action to your function whenever a monitor action is invoked:

$ngReduxProvider.createStoreWith(
  rootReducer, 
  middlewares,
  [window.__REDUX_DEVTOOLS_EXTENSION__({
    onMonitorAction: action => { if (action.type === 'CHANGE_LOCATION') changeLocation(action.location); }
  })])

[zalmoxisus]

Redux DevTools intentionally doesn’t redispatch actions to avoid side effects. So, except that middleware, the router needs something like this. Honestly, I don’t like such workarounds, so any suggestions of what we could do from our side, would be welcome.

What you wanted to do is possible by connecting the router to the extension as a separate instance, but that’s not an easy solution either, as you’ll have to reimplement the monitor actions, and not sure that having it decoupled from your main store is the case.

It seems that there’s an open issue there https://github.com/neilff/redux-ui-router/issues/49.