integration-guides

integration-guides copied to clipboard

Context

At first, we decided to build an integration for Laravel Scout by staying completely compliant/conformed with the original laravel/scout package. See meilisearch-laravel-scout.

The goal? To integrate this repository into the official laravel/scout package (as Algolia already is) by showing that people use it. This is now done! 🎉

But, despite this laravel-scout integration, we noticed some of the contributors would like a laravel-scout-extended integration, I mean with more friendly methods to handle settings in this repository, as this PR suggests. We refused this kind of PRs in meilisearch-laravel-scout since it would make our integration non-compliant with the official laravel/scout.

Decision with the community

According to this issue, and after the merge of the MeiliSearch support into Laravel/Scout, we have decided to:

• [x] deprecate the meilisearch-laravel-scout repo and redirect the user to the official laravel/scout repo.
• [ ] make a new repository laravel-scout-extended, like the one Algolia provides.

@curquiza Any progress or need any help developing the repo laravel-scout-extended. I was going to fork the Algolia one and work on modifying/stripping it to work with Meilisearch myself.

Hello @Braunson!

Thanks for this suggestion! We are not working currently on it, so any help is really interested!! 😄

People want the sort feature, see: https://github.com/laravel/scout/pull/537

Aggregates, multiple models from same index is something I found my self reaching for when using with Lighthouse graphql and its paginator.

Working around it by using meilisearch-php and querying directly for now. Some kind of a union or merge with primary key and a "type of model" field, but keeping the order/pagination.

https://github.com/algolia/scout-extended/blob/master/src/Searchable/Aggregator.php https://www.algolia.com/doc/framework-integration/laravel/advanced-use-cases/multiple-models-in-one-index/?client=php

Thanks for your comment @LiamKarlMitchell :)

Hi all!

As you probably know, Laravel Scout released a new version v9.5.0 which introduced a new ability to set Meilisearch's index settings :tada:.

So, my question is, for everyone watching this issue, do you think a laravel-scout-extended is still something worthy to be created? And which kind of feature do you expect to be present on it if your answer were "yes".

Thanks a lot!

Hello, this is great news !

I liked the artisan command scout:status which gives me lots of information as an overview:

• a list of all indexes
• model used
• synchronisation status
• record count

https://www.algolia.com/doc/framework-integration/laravel/production/get-status-overview/?client=php

So, my question is, for everyone watching this issue, do you think a laravel-scout-extended is still something worthy to be created? And which kind of feature do you expect to be present on it if your answer were "yes".

I'd love to see support of aggregates in order to implement a multi-model/global search.

Update: looks like the multi-search is missing to users: https://github.com/laravel/scout/issues/745

This is something it could be tackled by the laravel-scout-extended since it will not be supported: https://github.com/laravel/scout/issues/730#issuecomment-1516177995

Hi folks, is this actively being worked on? 😍

Hi, @MrThePlague hope you're doing well!

Unfortunately, even though the community highly requests it, we haven't progressed on this topic yet. It would be nice to have it, but we need more time to work on it. We are a small team that maintains more than 30 tools, SDKs and integrations, so it is pretty hard to make the time 😅

It would be nice if someone from the community could step in and start the project. We can provide help and feedback when needed.