Sign up to access "Build an E-Commerce Platform" right now.

Now there's a couple of important details around this. The first one is, of course, we don't want to store this if the user is not authenticated like we are at the moment, unauthenticated, because obviously we can't attach it to anything. And second of all, we want to make sure that we don't store the same address more than

once. So, if we had an address like A, B, and C, we don't want that to be stored more than once if the user types it multiple times. So let's figure this out.

Before we do anything, of course, we don't even have a model which represents a shipping address. Now, with this shipping address, of course, we want to attach this to an order as well, so it's a really important part of our app.

So let's go ahead and make a model here and just call this shipping address and, of course, we will generate a migration. So let's head over to create shipping addresses table and let's fill in the information that we need.

Now, of course, this can be attached to a user. So let's go ahead and say foreign ID and user ID. However, we want to store a shipping address because we want it to be attached to an order for a guest, but if the user is not authenticated and we store the shipping address, there's

going to be no user to attach it to. So we want to make sure we include nullable and we're going to set a constraint on this just for database integrity and then we can just fill the rest of the information in. So we're going to have a string for the address and let's fill in the city and, of course,

lastly, the postcode and, of course, feel free to update this with any other information you need. Okay, let's go ahead and migrate here and then we're going to head straight over to the user model and we're going to add in a shipping addresses relationship in here.

So this has many and the user has many shipping addresses and then we're going to do sort of the opposite of this for the actual shipping address itself and we know that this belongs to a user. So the user here, we're just going to say this belongs to and, of course, pass the user

model in. Okay, so now what we can do is actually create a shipping address in the database over here at checkout and then we can potentially attach it to the currently authenticated user. Let's first of all look at uniquely creating a shipping address regardless of how many

times we type the same one in. So we're also going to assign it at the same time, really important because we want to attach that to our order. So I'm going to assign that, we'll just set this to null for now, we'll go ahead and create

our shipping address property up here and, again, that could potentially be protected but we'll leave it public for now and this is going to be the result of the creation of the shipping address. So we're literally just going to grab the shipping address model and we don't want to

just say create because if we do that then it's always going to create it. So instead what we're going to do is say first or create. So that will always get that back but it will only create it on a certain condition with things that match and we're just going to go ahead and pass into here the shipping form

because that matches up with what we have in our database. Let's just check out what happens when we run this. So we'll keep our database open under our shipping addresses. Let's just store one of these.

So let's just say ABC like we demonstrated earlier, click confirm and pay and, yeah, the email address is filled as required so let's fill this in. There we go, yeah, of course, we've already got an account and, yeah, so we just need to add some details to our shipping address or change this up so we don't protect it but

let's go ahead and just set the fillable columns in here explicitly. You could say unguarded as well but let's go ahead and just add these in, city and postcode. Great and let's come over and just try this again. Okay, so let's switch this over to Billy again and there we go.

So we should have created that over in the database and we have. Now if we click it again, let's come over and give that a refresh, you can see it has not been created a second time, really, really important. We don't want to just keep storing the same address over and over again in the database.

Now we're going to change this up a little bit later because we need to take our pre-selected addresses into account eventually but this is enough for now. Now if we are signed in, we want to assign this to the user. We can actually do this all in one line.

So I'm going to go ahead and just wrap this in brackets so we can start to chain onto it and that is going to be a conditional user on this and then going ahead and associating the currently signed in user and then going ahead and saving it. So bear with me.

We'll go ahead and sign in and see how this works. So let's go ahead and log in and let's go over to our cart, hit checkout and let's do A, B and C, hit confirm order and pay. If we come over to the database now, you can see that has now been assigned to that user.

Now once again, this isn't perfect at the moment because we need to take into account the pre-saved addresses but if I just switch this up to say C, D, E and click confirm, that's also going to create the address and assign it to my user as well and this looks good.

Now there is one issue we need to fix up before we do anything. If we just take a look at our other users, we don't have any at the moment so I'm just going to go ahead and create another user in here just so we can demo this out. So let's save this.

So let's say Billy, completely unrelated to Alex and they have an address C, D, E. What's going to happen when I enter the same address? Well, the way that we've got it set up at the moment, it's going to look up this address and assign it back to me.

That's not what we want. We're effectively stealing someone else's address. If we click on this, you'll see what I mean. That's just switching it back to my user and then it will have disappeared from Billy's

account. So ideally what we want to do in here is have a little where condition. So we're going to say where belongs to and auth user and let's try this out. So let's go back to, set that to two, hit this again, come over.

That's not done anything. It's just recreated a second address attached to my ID. So that's a much better solution so we don't just swap user IDs around for each of the addresses.

And all of this is done in one line. It could have been done in a couple of lines. I just like doing things like this. Just makes a little bit more sense to me to sort of do it all in one thing, but feel free

to chop and change it around if you want to. Okay. So we'll tweak this a lot a little bit later. It's not perfect at the moment because like I said, we need to take into account a pre-saved

address as well, which we will do. That is for now storing a user shipping address, attaching it to a user if they are signed in and of course just saving it so we can eventually attach it to an order if they're not signed in.