Any large Flux application will have a lot of actions. This is why having action constants and sensible action names matter. The focus of this section is to discuss possible naming conventions for actions and to get organized with our actions. Constants help with reducing repetitive strings that are error-prone, but we'll also need to think about the best way to organize our constants. We'll also look at static action data—this will also help us reduce the amount of action dispatch code we have to write.
All actions in a Flux system have a name. The name is important because it tells whoever is looking at it a lot about what it does. An application where there are less than ten actions is unlikely to have a strong naming convention requirement, because we can easily figure out what these actions do. However, it's equally unlikely we'd use Flux to implement a small application—Flux is for systems that need to scale. This means that there's...