The dispatcher in Flux architectures is the single point of entry for new data entering the system. This makes it easy to fabricate mock data to help us churn out features faster. In this section, we'll discuss mocking existing APIs, and whether or not this is worthwhile to build into the action creator functions that talk to them. Then, we'll go over implementing mocks for new APIs that doesn't yet exist, followed by a look at strategies to substitute mock action creators for the real deal.
In order to mock data in a Flux system, the actions that are dispatched need to deliver this mock data to the stores. This is done by creating an alternative implementation of the action creator function that dispatches the action. When there's already an API that an action creator can target, we don't necessarily need to mock the data during the development of a given feature—the data is already there. However, the existence of an API that's used by an action creator...