In this section, we're going to reiterate the idea that we can change the implementation specifics of the various Flux components in our architecture. We'll start by talking about the dispatcher itself, and think about the various changes that we might make. Then, we'll think about stores and the enhancements we might want to make there. Finally, we'll discuss actions and action creator functions.
In Chapter 10, Implementing a Dispatche r, we implemented our own dispatcher component. The reference implementation by Facebook is perfectly fine to use, but it's not meant to be the de-facto component found in every production Flux architecture. Instead, it's meant to be a jumping off point, so we can see how the Flux dispatcher specification is supposed to work.
Our solution was to expose the dispatch() and register() functions from the dispatcher module. By doing so, we made using the dispatcher a little more direct in other areas of...