Sign up to access "Laravel Mentions" right now.

So it's a little less private than having this tucked behind a search, where when for example we say at A, then we want to send a query across to some other endpoint to only search for this query. And then we can perhaps limit the results on the back end somehow. So the question is, how do we do this?

Well, let's first of all just populate our database with a bunch of users. So let's come over and run phpr to certain tinker here. Let's grab our user. Let's use factory and let's really bump this up. So we'll bump this up to 5000 here and we'll go ahead and say create.

Now we know that over in our user factory, we've added our username. But what I'm also going to do is add in unique just so we don't get any collisions here. So let's go ahead and run this and we should be good. And let's go back over to here, type something in and yeah, there we go.

So we've got this huge list of users which we can start to filter down, but we don't really want this initial huge list. It kind of gets in the way and this is probably affecting the speed of our page load as well. And like I said, if we view the page source here and just take a look,

we're probably, let's just find out where this might be. And we've got all of these users in here now, this huge long list that now someone can look through. So really not ideal. OK, so let's figure out on the client side how to do this first of all.

So let's start over in our comment index. We will be building a plugin for this. We're going to duplicate the functionality initially, but we'll go ahead and build a plugin for this a little bit later.

So what are we doing at the moment? Well, we've got this mentionables class, which is fine for, you know, a couple of thousand users. Ideally, what we want to do is turn this into a callback where we can perform a search and return or set the results. So we still keep values. Nothing here changes.

But what we do is we instead we create this into a closure where we receive in text, which is essentially the query that we are typing as we press the trigger key and then start to type. And we have CB, which is callback. So we use this to invoke the callback to pass through the data and then that will get set into the values like we've already done.

So we want to basically pass this off. We don't need to do this, but we're going to pass this off to a function called user search. And into that, we're going to pass in the text. We're going to grab the users that we get back here.

I'm going to do a callback with them users to basically set them. So really, all that we need to do now is create our user search. Function in here that's going to take in the text and the callback, and we basically want to invoke the callback and pass through the array of objects into that.

They will then get set into values since we invoke callback here. So let's just try this out in a very, very basic way. So let's just say CB. And I'm just going to manually do this just so we know that we've got this working.

And let's say key Alex. And these need to be double quotes. And let's say value Alex. So there should just be one username here. Now, when we start to type. So let's say hey at. And there we go. We get the data in there exactly as we expected.

So the question is, what do we do now? Well, it really depends. We could use a standard fetch within JavaScript if we wanted to. We could use Axios since it's already loaded into Laravel. You can do pretty much whatever you want here.

We basically need to hit an endpoint, pass through the text that we're trying to search for and return a list of results. So let's start to build that out first. We can test that manually in the browser. So to do this, let's create out a controller. And this controller we'll call user search controller. We'll keep this really basic.

And you can go ahead and change this around if you want. So this user search controller's sole job is to just return a list of users based on a query that we pass in. So we're going to bring in our request object in here. We won't write a test for this, but we could later if we wanted to. So for now, let's just return user get. I'm just going to sort of take this step by step.

So user get. I'm going to register this under our web routes. We don't need to do this. We could register this under our API routes, but I'm just going to keep things really, really simple here. And I'm going to create our route here. It's going to again be a get route. And we're going to say user slash search. We're going to hook that up to our user search controller.

And that's pretty much it. So now we can just pass through a query here. Let's go ahead and duplicate this and we'll say user slash and search. And let's say query and we'll say AL just to see what comes back. OK, we get a 404. That's just because of the order that we have things in here, because remember, we've got a profile page here as well.

And it's making it basically look like we're trying to look for a profile called search. So there's a couple of ways that you could do this. You could either do a completely different URL. So users underscore search, or you could put this above here. Then you come into the issue where you can't have a user with the username search.

So I'm going to leave it like this. But just bear in mind, you might want to change the URL around. Let's head back over and give that a refresh. And there we go. OK, so, yeah, we need to pull in our user namespace. That's fine. Let's go over and do this now. Let's pull in our user model. Give that a refresh and we just get all of our users dumped out here as expected.

Now, we kind of want a better structure to this. So let's say user query just to pull this down to the next line. Let's grab these and then let's map through them, kind of like we did when we created our mentionables class a little bit earlier. So let's map through each of these users and let's return the kind of structure we're looking for. Because at the moment, it's just pretty much everything dumped out in here, which is not what we want.

So we're going to say key. That will be the user's name and value. That will be the user's username. Let's just make sure we've got this right. So over here, what do we do under the comments index? We set the key to the user's name and the value to the username. Yeah, so that's all good. OK, so if we now hop back over to the browser, give that a refresh, we now get a better structure to this with just the key and the value.

But of course, this is still not actually performing a search. Now, we're going to switch this over in the next episode to use Laravel Scout. If you are not using Laravel Scout or you don't want to use Laravel Scout, that is absolutely fine. You don't need to do this for something as simple as this. You could just say where username and you could say likes. You could just do a really quick search in your database for this and you could use percentage signs here to separate this out between,

let's say, the request and get queue. Otherwise, you would just have an empty string in there. So that will be enough to give you back just the results you need that match what you've typed in. It would probably be better to say that you wanted to search for the start of the query here, plus anything after it. That's going to give you more accurate results. So if we just give that a refresh, that's just going to give us any usernames that begin with a L.

So you can see here that the list is a lot more refined. And as we update this, it gives us some better results back. So that will do for now. But of course, later, we'll switch this over to Laravel Scout in case you wanted to. So let's hook this in to what we've built over in our search or our comment index. So what do we do here? We've already got Axios loaded into Laravel, so we don't need to do any setup here.

And we're going to say Axios get and we're going to go through to slash users slash search. And we're going to add on to the query string, the text that we get through into this callback. And then once that finishes, we get a response in here which will contain all of that data. And with that response, we then want to invoke this callback. So that callback goes directly into here.

And we've not given this any particular structure. So really, all we want to do is just say response dot data, which will just contain all of the data that we see here. And to be honest, that should be everything that we need to do. Let's head over and see this in action. So let's go over and say, hey, act. Now that will start to give us an initial list of users. Now we can change that around.

When we get to switching this over to Laravel Scout, it's going to be a little bit easier. But as I start to type now, you can see, sure enough, this starts to go ahead and filter this down. If we take a look at the network tab here, you can see each of these things as we type them. So let's say A-L-E-X. And yet, sure enough, we get this back in here.

Now, at the moment, what's happening, if we just take a look at this, you can see that we do get a bunch of results here. That's probably why I open the network tab. But we only see one result in here. Now, the reason that this happens is because when we do now specify the search, we want to specify the lookup and the fill attribute. So the lookup thing that we're going to use to look this up and display in the list is going to be the value.

That's going to be the key inside of the response that we get back. And similarly, we have a fill attribute as well, which is used to fill that value in. So now we should, if we search with a at Alex, we now get a much better list of everything that starts with Alex. Of course, we can just start to filter that down as we need. And it's a lot more convenient now.

OK, so we now have a relatively simple solution for going ahead and searching for usernames. If we want to bump this up and step this up a little bit, we probably want to use something like Laravel Scout with a third party search engine software. At the moment, what we're doing is OK, but it's not ideal long term. So let's go to the next episode, switch everything over to Laravel Scout, and then we'll go ahead and build this into a plugin so we can reuse everything that we've done a lot more conveniently.