Flux Architecture: Dumb Stores

[00:00] One improvement we could make to our Flux application is to get a lot of this logic out of our store and leave our store pretty dumb and just consuming an API of sorts. I'm going to delete all that and what I've done is, I've taken that exact same code and created a directory called API and there I've got a JavaScript file called cart-api.js.

[00:21] I've just converted those all to objects and object methods. We've taken our fore-loop that initially populates it and thrown it into this init method and we call that right before we export our cart API.

[00:35] Now back in our store we can just import that and update a bunch of these methods. Here we do cart-api.cart-items. We'll skip this one for right now. Here we'll return cart API totals and then on each of these method calls it'll just be from cart to API.

[01:04] This one here is a bit complex. It really looks like something that belongs in our cart API. I'm going to grab this and jump over to our API, jump that guy right there, cite this.catalog, object assign, this.cart-items, and we're looking good. Save that, and we'll jump back to our app store and this get-catalog and just return [inaudible] API, get-catalog.

[01:42] Let's try that out in the browser and it looks like everything is working just fine. I'm just going to jump around a bit, test everything out, increase, decrease, and remove and continue shopping. Everything's working just fine and our app store is a bit dumber, a bit easier to manage...