Skip to main content

Laravel Scout - multiple searchable arrays from one model

I am trying to create individual searchable arrays in Laravel Scout from a single City model, by iterating through its relationships. I have multiple fields returning arrays, all tied to the same hasMany relationship.

While Algolia can parse the arrays when returning search results, the presence of multiple arrays in the objects is causing the issue.

For instance, a current result is {city_name: 'Sydney', user_name: ['user_one', 'user_two'], user_id: [1, 2]}. The intended result is two objects: {city_name: 'Sydney', user_name: 'user_one', user_id: 1} and {city_name: 'Sydney', user_name: 'user_two', user_id: 2}.

Region->cities is a many-to-many relationship, and Region->user is a one-to-many relationship.

Since toSearchableArray returns a single searchable object, I've tried (unsuccessfully) to override it using searchable():

City.php:

public function users()
{
    $regionIds = $this->regions()
        ->has('users') // filters regions with no users
        ->pluck('id');

    return User::whereHas('regions', function($q) use ($regionIds) {
        $q->whereIn('regions.id', $regionIds);
    })->get(['name','id']);
}

public function toSearchableArray()
{
    $array = $this->to_array;

    foreach($this->users() as $user)
    {
        $array['user_name'] = $user->name;
        $array['user_id'] = $user->id;
        $array->searchable();
    }

    return [];
}

This returns Call to a member function searchable() on array when I attempt to index, as searchable() must be called on a query. I am trying to figure out a query that would allow me to attach a single User at a time via the Region relationship. Another possible option could be indexing the one object with the arrays, and building a splitter on both the user_name and user_id fields. Any help would be greatly appreciated!



source https://stackoverflow.com/questions/69382033/laravel-scout-multiple-searchable-arrays-from-one-model

Comments

Popular posts from this blog

Confusion between commands.Bot and discord.Client | Which one should I use?

Whenever you look at YouTube tutorials or code from this website there is a real variation. Some developers use client = discord.Client(intents=intents) while the others use bot = commands.Bot(command_prefix="something", intents=intents) . Now I know slightly about the difference but I get errors from different places from my code when I use either of them and its confusing. Especially since there has a few changes over the years in discord.py it is hard to find the real difference. I tried sticking to discord.Client then I found that there are more features in commands.Bot . Then I found errors when using commands.Bot . An example of this is: When I try to use commands.Bot client = commands.Bot(command_prefix=">",intents=intents) async def load(): for filename in os.listdir("./Cogs"): if filename.endswith(".py"): client.load_extension(f"Cogs.{filename[:-3]}") The above doesnt giveany response from my Cogs ...

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console...