- What is survos/search-bundle used for?
- It is a Symfony bundle from Survos that wraps mezcalito/ux-search-bundle and survos/field-bundle, providing configuration and integration helpers for adding search to an application. It focuses on connecting search services, indexing content, and querying results rather than shipping a search engine of its own. Think of it as a starting point for building a search experience in Symfony.
- Does survos/search-bundle work with Laravel?
- No. This is a Symfony bundle, so it registers a Symfony bundle class and is configured through Symfony's bundle and service configuration rather than a Laravel service provider. Composer will install it, but the integration helpers assume Symfony, not Laravel's container or config system. For Laravel projects, look at Laravel Scout with Meilisearch, Algolia, or a database driver instead.
- How do I install survos/search-bundle with Composer?
- Install it with composer require survos/search-bundle, which will also pull in its wrapped dependencies, mezcalito/ux-search-bundle and survos/field-bundle. With Symfony Flex the bundle registration is usually handled automatically; otherwise enable it in config/bundles.php. After that, add the bundle configuration and wire up your search service as described in the README.
- What dependencies does survos/search-bundle require?
- Its two stated dependencies are mezcalito/ux-search-bundle and survos/field-bundle, so the bundle is a thin integration layer over those packages. That means much of the real search behavior comes from the underlying bundles, and their requirements apply to your project too. Always check the composer.json of each package for exact PHP and Symfony version constraints before installing.
- Which Symfony versions does survos/search-bundle support?
- The package summary provided here does not list supported Symfony versions, so verify the require section of its composer.json on Packagist before adopting it. Because it wraps other Survos and Mezcalito bundles, your Symfony version must satisfy all of their constraints simultaneously. Checking the tagged releases is the fastest way to confirm compatibility with Symfony 6 or 7.
- How do I configure search services with survos/search-bundle?
- The bundle exists to provide configuration and integration helpers, so you typically register it in your Symfony app, publish or write its config block, and point it at the search service you want to use. The exact configuration keys live in the README and in the wrapped mezcalito/ux-search-bundle documentation. Read both before wiring services, since the wrapper mostly forwards configuration to the underlying bundle.
- How do I index content and query results with this bundle?
- The bundle's stated purpose is to help you connect search services, index content, and query results, so the normal flow is to index your documents or entities first and then run queries through the configured search service. The integration helpers are meant to reduce the boilerplate of that connection step. For concrete method names and index mapping details, refer to the README and the mezcalito/ux-search-bundle docs, which do the heavy lifting.
- Is survos/search-bundle production ready and actively maintained?
- It is a small Survos-maintained wrapper bundle, so review the repository's commit history, tagged releases, and open issues before relying on it in production. Because it is a thin layer, its practical stability largely tracks that of mezcalito/ux-search-bundle and survos/field-bundle. Pin a specific version in composer.json and run your own integration tests against your search backend.
- What are the alternatives to survos/search-bundle?
- You can use mezcalito/ux-search-bundle directly if you do not need Survos' field integration, or combine Symfony UX search components with a client such as Meilisearch, Elasticsearch, or Algolia. Laravel teams would typically choose Laravel Scout with a search driver rather than a Symfony bundle. If you want Survos' conventions around fields and search configuration, the wrapper is the convenience layer; otherwise the underlying packages give you the same core functionality.
- How should I test a search integration built with survos/search-bundle?
- Use Symfony's KernelTestCase or WebTestCase to boot the kernel with your bundle configuration, index a small fixture set, and assert on the query results your service returns. If hitting a real search backend is too slow or unavailable in CI, swap in a stub or fake implementation of the configured search client. Also run the underlying bundle's own test suite assumptions in mind, since behavior is inherited from mezcalito/ux-search-bundle.