Improved Search

[glennjacobs]

Admin Hub should not be aware of search engines, it just expects an interface to be implemented.

GetCandy will provide engines for Database, Meilisearch and Algolia.

The interface should allow for optional filters to be passed, to allow for customisations. But standard filters should be set in the interface.

Config sets the engine for each admin hub search requirement, as example below...

admin/search.php

    'engines' => [
        'products' => GetCandy\Algolia\ProductsEngine::class,
        'orders' => GetCandy\Hub\Search\Database\OrdersEngine::class,
        //.. etc
    ],

If a developer decides to use the database for Orders engine they probably don't want to be indexing order and customer information into the Algolia or Meilisearch engine. So we should make the indexing configurable.

Meilisearch and Algolia should be optional addons, e.g.

composer require getcandy/algolia
composer require getcandy/meilisearch

Database search engines are in the admin hub by default.

The Algolia package will likely want to take advantage of https://www.algolia.com/doc/framework-integration/laravel/getting-started/introduction-to-scout-extended/?client=php

Meilisearch has something similar planned, but it's not been implemented yet, see meilisearch/integration-guides#123

When documenting, Algolia and Meilisearch can have their own installation and configuration pages.
And for product retrieval documentation etc. we can have a single page showing examples for the QueryBuilder, Meilisearch and Algolia, using a tabbed system or similar.