flux-standard-action

I always put a `pending` property on the `meta` object, and any component that needs to show network status can just check that property on every render cycle. Aside from requiring some extra utility functions in the reducers to prevent having to updating `pending` for every state of the request it's rock solid and I haven't ever encountered a situation where it wouldn't work. You can get a _lot_ of mileage out of conforming to the FSA standard[1]; network status goes in meta, and errors are always handled the same way. [1] https://github.com/redux-utilities/flux-standard-action

I agree with that. When I first started with Redux and Flow, I was just following all the examples and made sure I used action creators for everything, even if there was no payload. Now I'm feeling more confident with Flux, and I recently realized that no, I don't need "action creators" for everything. That's silly. It's OK to just dispatch an object using your action constant directly. And then I found myself writing action creators on purpose, not because I saw it in some tutorial, but because it actually does remove some duplication. This was also missing from my education for a long time: https://github.com/acdlite/flux-standard-action#actions I had no idea why I was using a "payload" key, instead of just putting all the values in the top-level object. But this convention makes a lot of sense now.

Check out flux standard actions for even more consistency: https://github.com/acdlite/flux-standard-action