Action creator functions need to be organized, just as action constants are. In the preceding code examples of this chapter, we've organized both our action constants and our action creator functions into modules. This keeps our action code clean and easy to traverse. In this section, we'll build on this idea from the feature point of view. We'll look at why this is worth thinking about in the first place, then we'll talk about how these ideas make the architecture as a whole more modular.
Do we need to think deeply about modular action creator functions at the beginning of our Flux project? While the project is still small in size, it's okay if all action creator functions are part of one monolithic action creator module—there's simply no meaningful impact on the architecture. It's when we have more than a dozen or so actions that we need to start thinking about modularity and, in particular, features.
We can split our action creator module...