You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment I cannot use it with redux-observable.
So if I dispatch batched(action1, action2), redux-observable only receives the batchedAction. So not good. I could make the redux-observable to look into the batched actions, but I don't think is his job to do that. For example instead of listening to action1, will listen to
batchedAction and checks if inside contains action1, or
action1.
I think this is really bad as the epic should not care how a certain action is dispatched and this should be done to all epics because any action could be batched.
@manaflair/redux-batch made it in a way that works with redux-observable, please take a look.
The text was updated successfully, but these errors were encountered:
"You can add a middleware to dispatch each of the bundled actions. This can be used if other middlewares are listening for one of the bundled actions to be dispatched."
I've tested this together with redux-obervable and redux-observable-requests and it seems to parse each individual action as expected.
Edit
Only issue I'm seeing is the middleware can cause re-renders as it triggers listeners for each action in a batch. Perhaps the middleware could somehow tie into the native redux batch function?
At the moment I cannot use it with redux-observable.
So if I dispatch batched(action1, action2), redux-observable only receives the batchedAction. So not good. I could make the redux-observable to look into the batched actions, but I don't think is his job to do that. For example instead of listening to action1, will listen to
I think this is really bad as the epic should not care how a certain action is dispatched and this should be done to all epics because any action could be batched.
@manaflair/redux-batch made it in a way that works with redux-observable, please take a look.
The text was updated successfully, but these errors were encountered: