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

signed in. So we're going to tackle that first of all and just come over to the checkout template. And at the top here under account details, we're not going to need this at all if the user is signed in. So we can actually just go ahead and wrap this in a guest directive. So let's go ahead and end that directive there and pull that in. And at the moment,

we are signed out. So we see it, which is great. But as soon as we sign in, that's going to disappear. Now we can go ahead and validate this and say that it's required. But if we hiding it for a user that signed in, then surely is not going to be required because we're already signed in. So let's go ahead and just figure this out and how we're going to bind it in inside of our

component. And then we'll figure out the validation rules around that. So this is our input. We've got our validation error just down here, which we'll test out. Let's head over to checkout and we're going to create an array just up here and kind of separate out all of the sections here. So we're going to have our account form completely separate just to make things a little bit easier

to manage. And we'll go ahead and pre-fill this with just an empty string for the email. Now, if we come over to checkout, we can go ahead and use wire model in here. And we can really importantly defer this because we don't want to send a request through to Livewire for every single key we type and just say account form and email. Great. So that's all hooked up. Let's just make

sure this is hooked up by just going ahead and outputting the account form just up here. And yeah, of course, we just need to do a print R on this. And let's give that a refresh. And let's just type something. Now, at the moment, because we've deferred this, we're not actually going to see any value in here until we submit this. So just while we're testing this, why don't

we just create out a checkout method and just do nothing. And then over in checkout, let's go up here and say wire submit. And I think we're going to need to add prevent in there. And we'll just say checkout. And let's go over. Let's type our email in. Let's hit this. And there we go. So that now comes through, of course, because we have defer on there. So we're not making too many requests

to our back end. OK, so let's come down to where our account form is just here. And let's think about the validation for this. So there are lots of different ways that we can define validation out within Livewire. Let's just look at a really simple way of defining out a rules method. Now, I always tend to reach for a method because if, for example, you want to start adding custom

objects in here, like you had some sort of rule that you wanted to create, it's much easier if this is a method to start with rather than a property. You can define these as properties if you want to. So a much easier way is just to have a rules method that returns an array. So for account form.email, what are the rules we want to reply here? Well, we want this to be

required. We want this to be an email address. We want this to be a max255, for example. And really importantly, we want this to be unique to the users table because if the user is a guest and they're trying to use an email address that's already registered, we want to send them a very specific message and tell them they need to sign in. Of course, that's completely up to you, but

it makes more sense. So for this rule, we're just saying that it's unique on the users table for the email column. Now, if we just go and copy this just to keep things simple, we're going to create another method in here, which is going to contain the validation attributes to name these properly. In fact, let's use a method. Let's use a property for this

because I don't think it really matters too much. I'm just going to pop this up here. So this is going to be a validation attributes property. And we just define it in the same way. So account form email. What do we want this to be called? Well, we just want it to be called email address. And we can be a little bit

more specific with some of the other fields. So when we do show errors, it makes a little bit more sense. And then what we can also do is customize the validation messages, which is pretty important specifically for this unique account form email. So let's go ahead and say messages. And for this, for the unique rule, we want to say something like, in fact, I'm going to pull the copy over

that I have in my notes. And since you already have an account, please sign in to place an order. OK, great. So let's go over to our checkout page. Let's wrap this in our error check. So we're just going to say error account form email. And we can go ahead and end that error here. And in here, we can grab the message that's given if this is wrong. And that's just a single.

OK, so let's go over. Let's hit confirm. And it looks like at the moment that's not showing anything. Ah, we didn't call validate. That would help. So let's go ahead and actually explicitly call validate before we go ahead and create an order, process a payment, any of that kind of stuff. And there we go. The email address field. This is the attribute that we gave it is required.

If I go ahead and type in my email address, which I think is already registered. There we go. It seems like you already have an account. Please sign in to place an order. OK, so now we're going to head over and actually log in. So let's sign in with that account and let's see what happens. So we'll go over to our cart. Remember, the cart's transferred automatically here.

And if we check out, we don't see that information. But when I click, let's just die dump something so we can see that we're progressing past our validation. So let's just say create order. And let's come over. And nothing's happening. So obviously, the validation here is failing. But we obviously don't need to enter an email address because we're already

signed in. So there are a couple of ways around this. You can create a specific rule for this to ignore the email address if the user is signed in. That is, however, a little bit too complex. The easiest thing to do here would just be to pre-populate the email address here if the user is already signed in. So let's just go down to mount and just make this incredibly simple.

And down here, we're going to go ahead and grab the user at the same time. As not checking it, we can just grab the user. So we're kind of checking in this if statement and assigning it at the same time. And if that's the case, let's go ahead and assign the email in the account form to that user's email address. Great. So rather than a complex

validation rule, which doesn't really make sense because that's hidden, we can just go ahead and pre-fill it. When we click on this, we should see that we're checked out. Let's give that a refresh. And yeah, it's not working. So let's have a look here. Let's die dump on this user to make sure we actually have a user. And we do. So that should be being filled. And yeah, I think, yeah, okay.

So the reason that this is not working is because we've got this unique rule in here, but we're not excluding the currently authenticated user. Now to do that, just to give you a preview, if we just head over to users, my user ID is one. So what I could do is just do comma and one, and that would ignore that. So if we come back over and hit this, you can see it works and we can create an order.

But for this, we need to make this a little bit more dynamic. So what we can do is just concatenate onto the end of this, a quick check, auth user. And if that's the case, just do a comma. And if that's the case, just do a comma and then concatenate on the auth user's ID. Again, this is getting a little bit long, otherwise just an empty string. So basically, if the user is

signed in, output a comma with their user ID. And there's a load of different ways we can do this. We could pull the unique class in, which would probably be a little bit tidier. But let's get this working first of all. So there we go. We can create an order. That's great. And if we just go ahead and log out real quick, and of course, that's cleared out our cart, so we can fix that

up later. Let's go and just add another item to our cart and checkout. And let's enter my email address again, just to make sure that unique rule is still working. And there we go, it is. So for something that seemed pretty simple at the start, actually a little bit more complex, because we have to deal with two different states, the user being logged in and logged out.

But that is now our account details section done. And of course, you can add more details to that if you need to collect any more information from guests like their first and last name. Feel free to go ahead and add that information. Next, let's move on to validating our shipping form before we go ahead and pre-save addresses.