BlueWinds

// In this version, each reducer is very clear - for example, looking at billingReducer,
// we know all the ways that users can get credit. If a user ends up with an invalid credit amount,
// we can easily start looking in the billingReducer to know all the places this could have come
// from.

// On the other hand, looking at VIEW_PERFORMER, it's not clear what exactly happens when the action is
// emitted. We have to go look at every reducer (or at least grep them) to know what the aciton is doing.
// Also note how 'VIEW_PERFORMER' needs extra context attached - it's not clear, looking at the action creator,
// why it needs purchaseHistory attached. What does that have to do with viewing a performer?