markerikson
commented
4 years ago Original date: 2017-02-05T21:21:28Z
Thanks! And good questions, as usual :)
The question of where to put logic comes up fairly frequently, which is why I wrote an FAQ entry on the topic: http://redux.js.org/docs/fa... .
It would be a valid approach to dispatch, say, a `PILOT_EDIT_CANCEL` action, and have the reducers respond by doing the multiple various things needed in response. I've opted to go the route of having more "primitive" actions that can be reused and composed in various use cases.
Per your question on "inconsistent states", my "Idiomatic Redux: Thoughts on Thunks" post actually addresses that question specifically. See this section: http://blog.isquaredsoftwar... .
Original author: Daniel @danielmartinprieto
Original date: 2017-02-05T20:14:22Z
Hey, awesome post, as usual! I have a question regarding thunks, as I've seen you commenting about this on Twitter before: shouldn't these thunks be just normal action creators dispatching only one action type, letting the different reducers handle the logic? I understand you can place this logic in both places (action creators or reducers), but in this case, if something happens in the middle of two dispatches in a thunk, we'd have an inconsistent state, right?