"Dispatching while constructing middleware" error with Redux ^4.0.0 about redux-most HOT 3 CLOSED

Thanks. This is because of the init action I'm dispatching. I had an idea for it originally, but never ended up making use of it. So, I will probably just remove it altogether...... but will need to make this a breaking change just in case anyone was watching it in their apps as a signal to do something.

If you'd like to add this to your #29 PR, I will merge it together. If not, I can do it.

It's basically just deleting the EPIC_BEGIN constant from the constants file + the epicBegin action creator + removing the import & this middlewareApi.dispatch(epicBegin()) line in createEpicMiddleware.

from redux-most.

I can do it. What about the EPIC_END action. Should we get rid of that as well, since there's no EPIC_BEGIN anymore?

from redux-most.

No, I think that should stay. It's something I borrowed from redux-observable. That one has more of a purpose. It's to use as a trigger for initiating any sort of cleanup work you might want to do when using the replaceEpic method (hot reloading is the most common use case for this, but there are others.)

That one fires only later on. So, it's unrelated to the new code they added in Redux that's causing the error you're seeing. EPIC_BEGIN is fired during the construction phase though.

from redux-most.