December 23, 2016
I've heard people talk about ngrx/store and Redux for the past 2 months but honestly I was always busy and I didn't have time to experiment it.
Finally yesterday I decided to take a look at it and well… I can say that I’m really impressed and I don't think that I'll write applications without it.
It's called redux because it deals with the concept of reducers:
@ngrx/store builds on the concepts made popular by Redux and supercharges it with the backing of RxJS. Each application built around store will contain three main pieces:
The store records all the information of the application. The store itself is an observable that we can access with operators like map, filter, reduce, etc.. . It promotes the idea of one-way data flow and explicitly dispatched actions. The only way to initiate a state update in your application is through dispatched actions, corresponding to a particular reducer case.
The reducer is a pure function accepting two arguments.
- the previous state
- an action with a type and optional data (payload) associated with the event
The action allows us to communicate to our reducers when state needs to be updated.
Let's do an easy example to better understand how it works. We have a restaurant with 3 tables where the first one has 4 seats, the second one 6 and the third one 8 (small restaurant but it works really well :) ) :
The customers can book a table:
they can cancel the reservation or be seated when they arrive at the restaurant.
The live example is available here (http://www.dzurico.com/book-table/index.html) and the source code here: https://github.com/daniele-zurico/table-order ( I pushed 2 branches: master with the orginal code and feature/ngrx-store using @ngrx-store)
The app.module.ts initialise the StoreModule passing the reducer (line 23 to 26):
The PersonListComponent is the main component of the application:
As you can see it is really short, however there're 2 sections really important:
- Line 39-45: we dispatch the actions passing result.action (BOOK, SEAT and CANCEL - passed from the dialog component) and a payload that contains all the data that we need: booking name, number of guests, table id and number of seats.
- Line 23-26: we subscribe on all the changes of the table store and we pass the data to our local variable "people" (used to populate the view).
The last piece of our application is the reducer:
- Line 6-37: we initialise the 3 tables and we pass the value to line 39 (Initial state)
- Line 39-87: based on the action dispatched we book the table, we seat the guests or we cancel the reservation.
Of course this post doesn’t show all the features of this amazing library but if you want to become a master have a look on the official documentation.
If you enjoyed this post follow me on twitter @Dzurico!