You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This maybe would allow that laravel scout can use any search engines which is supported by SEAL without having to implement the search engines by there own.
Differences between Laravel Scout vs SEAL
The main difference between Laravel Scout and SEAL is that in Laravel Scout the mapping, field configuration, ... is optional and there exists not an abstraction around it. So if you have searchable, filterable, ... fields that definitions are not defined in an abstract way instead they requires to be defined inside a specific meilisearch configuration: https://laravel.com/docs/10.x/scout#configuring-filterable-data-for-meilisearch.
So the most difficult part to have a seemless integration of SEAL Adapter into Laravel Scout would be that project using the SEAL adapter requires still defining the mapping.
There are 2 options where the mapping could be defined.
Solution A
It is configured inside a configuration file which entity mapped to which SEAL schema e.g.:
Add support for Laravel Scout by providing a bridge to it.
This maybe would allow that laravel scout can use any search engines which is supported by SEAL without having to implement the search engines by there own.
Differences between Laravel Scout vs SEAL
The main difference between Laravel Scout and SEAL is that in Laravel Scout the mapping, field configuration, ... is optional and there exists not an abstraction around it. So if you have
searchable
,filterable
, ... fields that definitions are not defined in an abstract way instead they requires to be defined inside a specific meilisearch configuration: https://laravel.com/docs/10.x/scout#configuring-filterable-data-for-meilisearch.So the most difficult part to have a seemless integration of SEAL Adapter into Laravel Scout would be that project using the SEAL adapter requires still defining the mapping.
There are 2 options where the mapping could be defined.
Solution A
It is configured inside a configuration file which entity mapped to which SEAL schema e.g.:
Solution B
We introduce a new kind of metadata loader which alloes to definition of the mapping on Laravel Eloquent Model itself e.g.:
The text was updated successfully, but these errors were encountered: