Join egghead, unlock knowledge.

Want more egghead?

This lesson is for members. Join us? Get access to all 3,000+ tutorials + a community with expert developers around the world.

Unlock This Lesson
1×
Become a member
to unlock all features

Level Up!

Access all courses & lessons on egghead today and lock-in your price for life.

Autoplay

    Simplify Collection Management with ngrx Entity in Angular

    Lukas RuebbelkeLukas Ruebbelke
    angularAngular
    ^7.0.3
    ngrx-store@ngrx/store

    Data manipulation on collections can be expensive because it is usually necessary to iterate over the collection at least once to perform any kind of update or selection to it. A common pattern for avoiding expensive iterations is to break a collection into a key-value store that allows for instantaneous lookup of value provided you have the key. We could handle this data transformation ourselves but ngrx entity was created to do all the heavy lifting for us. In this lesson, we will see how to update how we define our feature state to use EntityState, create an EntityAdapter, define our initial state using our adapter and most importantly, how to leverage the convenience methods that the adapter gives us in our reducer. We will also examine how ngrx entity changes the shape of our state by splitting our collection into ids and entities and how to update our feature selector to work with it.

    Code

    Code

    Become a Member to view code

    You must be a Member to view code

    Access all courses and lessons, track your progress, gain confidence and expertise.

    Become a Member
    and unlock code for this lesson
    Discuss

    Discuss

    Transcript

    Transcript

    Instructor: In this lesson, we are going to learn how to simplify our collection manipulation with NgRx entity. Working with collections as a whole can be a little bit difficult when you need to either find a selected item or delete or update an item.

    Usually what that means is you have to iterate over the collection until you find the thing that you need and then perform your operation. If you're doing this over and over and over, that can be very expensive.

    A common pattern is to break your collection into a key-value store. Therefore, if you have the key or the ID for your object, then you can look it up in almost real time and find that object, manipulate it or delete it or whatever you need to do. Then, move forward. Having to iterate over a collection over and over is very, very time-consuming.

    We are going to integrate entity into our application. The first thing we need to do is we're going to add the ability to load project. We're going to have to do a little bit of groundwork here to get this working. It'll be worth it in the end.

    The first thing we'll do is add in a load projects projects action type for projects load data. Then we're going to just create an action object for this particular action type. We'll call this load projects. This will implement the action interface. We'll set the type.

    We'll also set the constructor initially. When we say load projects, we're going to pass in the projects that we want to load, which we will pull from the initial projects once we move over to the reducer.

    Now that we have our load projects action defined, let's go ahead and add this to the union type. Then from here, let's hop into our projects reducer. We're going to change a few things here. The first thing that we're going to do is we're going to move away from this custom interface that we created at the beginning.

    Let's go ahead. Let's take this project state interface. Let's rewrite this. We're still defining an interface. It's going to project state. It is going to extend the entity state that ships with NgRx entity. It's a generic. It will take a project object.

    Then we're going to define our custom property on here, which is selected project ID. Under the hood, it's going to assume that it's dealing with a project in a collection of projects.

    You can look here in the entity state interface that it has two main properties, IDs and entities. When you send in your collection, under the hood, it will break it up into that key-value store for you where it will have a key-value store as well as it keeps track of the IDs in the IDs array.

    The next step that we need to do, instead of defining our initial state, is we need to initialize our entity adapter. We're going to create an adapter. It's going to be of type entity adapter. Because it's generic, we'll give it a project property. Then we'll go create entity adapter. Again, type the generic portion of this. There we go.

    Now we are ready to define our initial state. Because that the IDs and the entities are handled under the hood, what we're going to do is instead pull initial state off of the adapter that we just created and then define the additional custom properties that we want to put on our initial state. In this case, it's going to be just selected project ID. We'll go ahead and set that to null.

    Now that we have our adapter defined, we'll go ahead and export the initial projects so that it is available outside of the application so that when we call load projects, we can pass that in. That's just a temporary step.

    Now we'll go down to the reducer. We can get rid of some of these manual methods that we created, create project, update project, etc. We can start to replace these with some convenience functions that were provided to us from the entity that we created.

    Project selected is going to be the odd one here. Instead, we're just going to return a brand new object. Using object at assign, we're just going to update the selected project ID. This is the one odd one because we're not dealing with the collection itself but the custom property that we created.

    Now what we'll do is, because load projects, add projects, update projects, and delete project are going to be pretty much the same, let's go ahead and let's gut these switch cases here.

    We are going to replace them with a new simplified version that's available to us because of the entity adapter that we created. We're just going to return adapter.addmany. We'll pass in the action payload and state.

    In this case, we're saying, "Hey, we wanna add many of, many projects if you will to the collection. And then from here, we will add in add one, upsert one, and then we will do remove one." Now that we have that available, let's go ahead, hop into our barrel load.

    We're just going to make initial projects available to our application. What we're going to do now is just manually pass that in when we fire off a load projects action. We go into projects component. Let's go ahead and get projects. Let's dispatch a load projects action, new load projects. We will pass in initial projects. We should be good to go.

    Let me just make sure that this imported correctly. It did.

    Now let's delete this selection within the observable stream because the underlying structure is going to change. Let's go ahead and trace this out. We can see what we're working with, projects async pipe JSON. Remember, we're dealing with IDs and entities. Let's trace this out.

    You can see here that this is an entirely new collection. Within the observable stream, we need to change how we're servicing the data that we need. First things first, let's go ahead and map data entities. You can see now that we have a key-value pair that we can work with.

    Let's go ahead and do one more map operation. We're just going to pull the keys off, loop over it, and then assign it to the underlying object. We'll go objects.keys map. Then we'll return data. This is basically a line for this instantaneous lookup.

    Now if we go into our browser, let's take a look. Now we're dealing with an array. Map returns an array. Then we're populating with the value based on the key. We can uncomment this, delete this statement here. We should be good to go.

    One thing that we do need to do as well is that, because we're using the entity to delete it, we need to send in the ID. We can go ahead and get rid of this.getprojects because we no longer need to rehydrate this every single time we do an operation. Now we can go and see that if we select this, that we can delete it.

    Now any kind of operation that we do, create, read, update, and delete, is now being handled by NgRx entity and via these convenience functions that we surfaced in our reducer. We added the load projects action type. Then from there, we redefined our basically feature state via the entity state interface.

    We initialized the adapter using create entity adapter. Then we set our initial state using adapter.getinitialstate and sending in our custom property. Then, the best part of all is that we were able to, in our reducer, defer this workload to the adapter itself and not having to use our home-brewed immutable functions that we had to create.

    Then surfacing initial projects and load projects, we can now in our component, start to go through and, now call load projects, send in initial projects which then is going into the reducer and populating that.

    The one thing that we had to do that I think is a bit messy still is we had to add an additional step to manipulate the data into something that we could actually use. This is how you integrate NgRx entity into your Angular application.