Chapter 4. Creating Actions
In the previous chapter, we worked on building a skeleton architecture for our Flux application. The actions were directly dispatched by the dispatcher. Now that we have a skeleton Flux architecture under our belts, it's time to look more deeply into actions, and in particular, how actions are created.
We'll start by talking about the names we give actions and the constants used to identify the available actions in our system. Then, we'll implement some action creator functions, and we'll think about how we can keep these modular. Even though we might be done with implementing our skeleton architecture, we may still have a need to mock some API data—we'll go over how this is done with action creator functions.