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

This requires a minimum, which we've set to zero and a maximum. Now, this maximum needs to be the maximum price or the highest price within this category. Now, behind the scenes, I've gone ahead

and changed Nike Air Force 2 to $120 and I've gone ahead and in my editor or my terminal, run phpscout import. We need to make sure that we run that artisan command to update this in Metasearch so we can actually query it properly.

So once you've got two different products of two different prices, the first thing that we really need to do is find out this max. Now, just to demo this out, let's go ahead and set this to something like $50,000.

And let's go over to our product browser and create our public property, which will keep track of this value within this slider. So I'm going to go ahead and call this price range. We could technically put this information inside of our query filters,

but we'll separate it out just so it's a little bit easier. Now, the max in here, we don't know at the moment. We're going to set this to a default of the highest priced item, but we don't know what that is just yet or how to get that.

So just while we're demoing this out or just while we're playing around with this, let's do that print R again just to grab out the price range just so we can see that and yeah, so let's go ahead and use print R here. There we go.

So the first goal is to work out the maximum price item and put that within the slider so we can see that value. So to do this, let's go down or we can do this amount actually. And let's go ahead and say this price range and max and set that to this

category, grab the product from this category and then go ahead. And because this is a Laravel collection, we can use the max helper or the max method on this to grab out the max price range. So that's going to set that by default into that price range of max.

If we give that a refresh, sure enough, we've got one hundred and twenty thousand or twelve thousand. Sorry for one hundred and twenty dollars. Now we've done this in here.

But what we also need to do is pass this down so we can put this within here. The max price is always going to be a static value. It's never going to change because we're only ever going to have one highest product price regardless of the filters

that we apply. So what we can actually do is we can move this down. Into our search just here, so let's put it down just under here and then that should be just about it, we'll need to make a tweet to this in a minute. But what we can also do is create out a variable called max price,

set that to here, the maximum price within that category, set that as an initial value on our price slider, but also pass down the max price on its own so we can add that to our HTML slider. Let's say max price.

So first thing to do, grab the max price of any of the products, not the products that we filtered, because that's going to vary. We want the overall maximum price. Set that as the default value,

default value to the price range slider and pass the max price down. And with that max price, we're going to put that into here. Like so. And what we can actually do now is we can

update the value of the slider in here by using the money helper and then saying price range max, because we know that's going to be filled now, because it's going to be set initially to the maximum highest price product. So if we click on that, we now get $120 in here and we get our slider.

And if we just inspect this, you can see that we've got a max of one hundred or twelve thousand. So the only problem is we're not hooking this slider up at the moment. We can change the value of it, but we're not hooking this up anywhere.

So that's very easy. Just with wire model, we can go ahead and set that to price range. And I think we'll just say dot max. Let's go over, give that a refresh and there we go.

So by default, this is now set to one hundred and twenty dollars. And if we move this down, it updates. But you can see that when I adjust this, it just bumps right back up to the star.

And the reason for that is down here, we're always setting this on every render to the max price. This is going to be one hundred twenty dollars wherever we move it. So what we want to do is we want to say, well, if it's already got a value.

So if the price range max already has a value, then use that. Otherwise use the max price. So now we start off with the maximum price, but then we can adjust this further down and filter by max price.

So now that we've got that maximum price in there, of course, what we can do is apply this to Melissa to only show products with that in there. So just under where we apply our filters, let's go ahead and say if this price range max, so we only want to do this if we've got

something set in there, which we should always have, then we're going to say options filter, which remember we've already set. So we're going to have to concatenate onto this. And then we want to set that something like and price.

And we want to say less than or equal to a certain value. Let's just set that to ten thousand for now, just so we can test this out. And if we come over and give this a refresh, that doesn't look like it's working at the moment.

So let's just adjust this maybe and we get undefined a raky filter. That's just because we're only applying this if we've got filters. Therefore, at this point it doesn't exist. So just to get around this, let's go ahead and always add in a filter key.

But we'll set this to null. We won't set it to an empty string because Melissa won't like that. We'll set it to null to start with. So if we come over now and we filter this,

this should now be being sent down to Melissa. Great. So we now end up with this error and we can demo this by just dying and dumping on options and filter. And what we will see is if we come back

and give this a refresh, get rid of this and then pull that back. When we slide this, because we don't have any variation filters, this filter starts with the and operator. So that's not what we want.

We want to kind of get rid of this and operator before we start sending it through if there aren't any filters in there. Now, there's probably a much cleaner way to do all of this. But let's just add this in line here.

When things start getting a little bit more complex, we know it's time to refactor, but we'll just keep it simple. So let's say if there are filters already or even if options filter is in there already and we could use an is set on that to be a little bit more explicit.

Then we want to go ahead and concatenate on and to this. So let's concatenate on. Wrap this in brackets, we'll go over this in a second. Otherwise, an empty string.

So basically set the filter if we already have filters with a prefix of and and that would be like that and that. And otherwise don't prefix anything. And we could actually get rid of that space there and do that.

So we end up with and before price and after what we've already got in our filters, otherwise we just end up with price on its own. So let's try this out. Give this a refresh and let's just close this off and just try to filter something.

And yeah, price is not filterable. So we need to go ahead and add this over in postman. So let's head over to postman. There's going to be an easier way to do

this a little bit later directly within Laravel. But let's add price in there and send that across. And let's go back over and try this again. And we should be there.

So let's scroll down and there we go. Great. So if we just sort of go as a max price of one hundred and one eighty, of course, that includes the Nike Air Force one. But if we go all the way up to the top to one twenty, we should include the other shoe.

Now we don't at the moment because we've said greater than or equal to this hard coded value that's going to be the actual price range slider. So as soon as we fill this in, we should be good to go. So let's say price range and max.

And that's getting a little bit long, but not to worry. If we come over now and we pull this down, that is looking good. So we can really filter down. Now we get to the point where there are

going to be no products that match our filter and we can start to clear up some of these filters in here, which we'll do in a second. But at least now our price range slide is working. And of course, if you had more products, this would be a little bit more dynamic.

OK, so we've got our price range slider working with a little bit of complexity here, which, of course, we can refactor later. Let's go over to our product browser, get rid of our price range dump out here. And let's just go down to the point where we don't have any products in.

And let's get rid of these two things here. So the condition that we want to show our filters on is if we actually have any products, it makes sense to only show this if we have products. So let's just wrap all of this in an if

statement and we'll just say if products and count. It's really as simple as that. So let's pull this for each in and just end that for end that if there. And then when we go down to the point where we don't have any products,

there we go, found no products matching your filters. And of course, you can output anything there if you want to. OK, there we go. There is our basic price slider now working with that request over to Metasearch.