The Mezcalito UxSearch Bundle provides an easy-to-use classic search and faceted search system in your Symfony application using Twig Components and Live Components. It allows you to create and manage multiple search, each with its unique configuration. Currently, the bundle supports Doctrine and Meilisearch adapter.
Add mezcalito/ux-search to your composer.json file:
composer require mezcalito/ux-search
If you are using Symfony Flex, the following steps should be done automatically. Otherwise, follow the instructions.
Inside config/bundles.php
, add the following line:
// config/bundles.php
return [
// ...
Mezcalito\UxSearchBundle\MezcalitoUxSearchBundle::class => ['all' => true],
];
To configure the bundle, add the following configuration to your config/packages/mezcalito_ux_search.yaml
file.
This example demonstrates how to set up a Meiliseach adapter:
mezcalito_ux_search:
default_adapter: 'default'
adapters:
default: '%env(MEZCALITO_UX_SEARCH_DEFAULT_DSN)%'
orm: '%env(MEZCALITO_UX_SEARCH_ORM_DSN)%'
For now, only 2 adapters are available: Meilisearch and Doctrine.
Adapter | DSN |
---|---|
Meilisearch | meilisearch://key@localhost:7700 |
Doctrine | doctrine://default |
Read the Meilisearch part docs and the Doctrine part docs to learn about the configuration options available for each adapter.
You can also create your own Adapter to use other provider.
To use the bundle, create your first Search
. To do this, simply create a class and add the AsSearch
attribute.
In the case of Meilisearch, you need to specify the name of the index to use, and for Doctrine, the FQCN of the entity to use.
By default, the name of your search will be the name of your class with the Search
suffix removed. You can change this by specifying a custom name.
Also, by default, the Adapter used is the one specified in the configuration under default_adapter
. You can specify the name of the Adapter to use, for example, if you have multiple Search
instances that use different Adapters.
<?php
declare(strict_types=1);
namespace App\Search;
use Mezcalito\UxSearchBundle\Attribute\AsSearch;
use Mezcalito\UxSearchBundle\Search\AbstractSearch;
#[AsSearch('products')]
class ListingSearch extends AbstractSearch
{
}
If you wish, you can add facets to your Search. To do this, you need to use the addFacet
method.
This method takes the following parameters:
Parameter | Description | Type | Required |
---|---|---|---|
property | Property name | string | ✅ |
label | Label displayed | string | ✅ |
displayComponent | FQCN of your Twig component | string | ❌ |
props | Props to pass to component | array | ❌ |
<?php
declare(strict_types=1);
namespace Mezcalito\UxSearchBundle\Tests\TestApplication\Search;
use Mezcalito\UxSearchBundle\Adapter\Meilisearch\MeilisearchAdapter;
use Mezcalito\UxSearchBundle\Attribute\AsSearch;
use Mezcalito\UxSearchBundle\Search\AbstractSearch;
use Mezcalito\UxSearchBundle\Search\Facet;
use Mezcalito\UxSearchBundle\Twig\Component\Facet\RangeInput;
#[AsSearch('products', name: 'listing', adapter: 'meilisearch')]
class MeilisearchSearch extends AbstractSearch
{
public function build(array $options = []): void
{
$this
->addFacet('type', 'Type')
->addFacet('price', 'Price', RangeInput::class)
->addFacet('price', 'Price', null, ['limit' => 20])
;
}
}
You can also add sorting options to your Search. To do this, you need to use the addAvailableSort
method.
This method takes 2 mandatory parameters:
Parameter | Description | Type |
---|---|---|
key | Attribute key and order separate by ':' | ?string |
label | Label displayed | string |
If you do not specify a sort or if the key is empty, the default sorting of your adapter will be applied.
use Mezcalito\UxSearchBundle\Search\Sort;
// ..
public function build(array $options = []): void
{
$this
// ..
->addAvailableSort(null, 'Relevancy')
->addAvailableSort('price:asc', 'Price ↑')
->addAvailableSort('price:desc', 'Price ↓')
;
}
For example, you can modify the ResultSet
on the PostSearchEvent
to enrich a Hit
with data from database.
use Mezcalito\UxSearchBundle\Event\PreSearchEvent;
use Mezcalito\UxSearchBundle\Event\PostSearchEvent;
// ..
public function build(array $options = []): void
{
$this
// ...
->addEventListener(PreSearchEvent::class, function (PreSearchEvent $event) {
// $event->getSearch();
// $event->getQuery();
})
->addEventListener(PostSearchEvent::class, function (PostSearchEvent $event) {
// $event->getSearch();
// $event->getQuery();
// $event->getResultSet();
})
->addEventSubscriber(YourEventSubscriber::cass)
;
}
It is possible to enable a URL rewriting system to allow sharing of configured search URLs. To do this, simply add the ->enableUrlRewriting
method. By default, a DefaultUrlFormater
is provided in the bundle. This allows you to add query parameters with the values of the selected facets.
public function build(array $options = []): void
{
$this
// ...
->enableUrlRewriting()
;
}
You can also create your own UrlFormater. To do so, you need to implement the UrlFormaterInterface
and define your own logic in the generateUrl
and applyFilters
methods. All that is left is to use it in a search via the ->setUrlFormater()
method.
use App\Url\YourCustomUrlFormater;
// ...
public function build(array $options = []): void
{
$this
// ...
->enableUrlRewriting()
->setUrlFormater(YourCustomUrlFormater::class)
;
}
To render a search in your Twig template, you can use the Mezcalito:UxSearch:Layout
, you will then have a default rendering provided by the bundle.
{{ component('Mezcalito:UxSearch:Layout', { name: 'listing' }) }}
<twig:Mezcalito:UxSearch:Layout name="listing"/>
In both cases, replace listing
with the name of search configuration.
<div {{ attributes.defaults({
'class': 'ux-search',
'data-controller': 'ux-search',
'data-loading': 'addClass(ux-search--is-loading)'
}) }}>
{% block content %}
<div class="ux-search__inner">
<div class="ux-search__form">
{% block form %}
<twig:Mezcalito:UxSearch:SearchInput />
{% endblock %}
</div>
<div class="ux-search__toolbar">
{% block toolbar %}
<twig:Mezcalito:UxSearch:CurrentRefinements/>
<twig:Mezcalito:UxSearch:ClearRefinements />
<twig:Mezcalito:UxSearch:SortBy/>
{% endblock %}
</div>
<div class="ux-search__facets">
{% block facets %}
{% for facet in search.facets %}
<twig:Mezcalito:UxSearch:Facet :property="facet.property" />
{% endfor %}
{% endblock %}
</div>
<div class="ux-search__listing">
{% block listing %}
<div class="ux-search__stats">
{% block stats %}
<twig:Mezcalito:UxSearch:TotalHits/>
{% endblock %}
</div>
{% block hits %}
<twig:Mezcalito:UxSearch:Hits />
{% endblock %}
{% block pagination %}
<twig:Mezcalito:UxSearch:Pagination />
{% endblock %}
{% endblock %}
</div>
</div>
{% endblock %}
</div>
You can tailor the behavior and appearance according to your needs by overriding default component or implementing custom logic. This allows you to adapt the bundle to your specific use cases and requirements.
Component name | Description |
---|---|
Layout | The root wrapper component for all components |
CurrentRefinements | Displays a list of refinements applied to the search |
ClearRefinements | Displays a button that lets users clean every refinement applied to the search |
SearchInput | Let users perform a text-based query |
SortBy | Displays a list of sorting possibility, allowing a user to change the way hits are sorted |
TotalHits | Displays the total number of matching hits |
Pagination | Displays a pagination system which lets users change the current page of search results |
Facet/RangeInput | Allows a user to select a numeric range using a minimum and maximum input. |
Facet/RangeSlider | Provides a user-friendly way to filter the results, based on a single numeric range |
Facet/RefinementList | Users can filter the dataset based on facets |
Hits | Display a list of results. |
Please report issues and request features at https://github.com/mezcalito/ux-search/issues.
This bundle is under the MIT license. For the whole copyright, see the LICENSE file distributed with this source code.