- Can I use this bundle with Laravel’s Lighthouse GraphQL package?
- Yes, but with adjustments. The bundle relies on Symfony’s resolver pattern, while Lighthouse uses schema-first definitions. You’ll need to bridge the two by creating custom resolvers or using Lighthouse’s resolver extensions to integrate Atoolo’s search queries. Start by reviewing Lighthouse’s resolver documentation and the bundle’s resolver factory examples.
- What Laravel search backends (e.g., Scout, Algolia) are supported?
- The bundle depends on Atoolo’s search infrastructure, which isn’t natively compatible with Laravel Scout or Algolia. You’d need to create adapters to translate Atoolo’s query DSL (e.g., facets, spatial filters) into Scout’s or Algolia’s APIs. Algolia’s Laravel SDK might offer easier integration, but custom logic will be required for full feature parity.
- Does this bundle work with Laravel 10 and PHP 8.4?
- Officially, the bundle supports PHP 8.1–8.4, but Laravel 10’s PHP 8.2+ compatibility should work. Test thoroughly, as the bundle’s Symfony dependencies might introduce edge cases. Check the [PHP 8.4 badge](https://github.com/sitepark/atoolo-graphql-search-bundle) and review the [E2E tests](https://github.com/sitepark/atoolo-e2e-test) for Laravel-specific issues.
- How do I add custom search fields (e.g., `staticImage`) to existing GraphQL queries?
- The bundle supports dynamic field additions via resolvers and factories. Extend the schema by defining new fields in your GraphQL server’s configuration (e.g., Lighthouse’s `schema.php`) and map them to Atoolo’s search resolver. Ensure your Laravel schema migrations account for these new fields to avoid conflicts during API evolution.
- Will this bundle break my existing GraphQL queries?
- No, if configured correctly. The bundle extends the schema without modifying existing queries. However, schema conflicts can arise if you’re using strict tools like Overblog’s GraphQL Bundle. Test with Lighthouse or GraphQL PHP, which offer more flexibility for resolver-based extensions. Always validate queries post-integration.
- What are the performance implications of server-side query execution?
- Server-side execution (v1.9.0+) adds latency but improves search relevance. In Laravel, mitigate this by caching frequent queries (e.g., Redis) or using OPcache for resolver logic. Monitor query batching (e.g., GraphQL Relay) to avoid N+1 issues. Benchmark with your search backend to optimize.
- Are there alternatives for Laravel GraphQL search with less integration risk?
- Yes. For Scout users, consider adding custom GraphQL filters via Lighthouse’s `resolveField` or GraphQL PHP’s `resolveFn`. Algolia’s Laravel SDK supports GraphQL natively, while Meilisearch offers a Laravel wrapper. These avoid Atoolo’s dependency overhead but may lack advanced features like faceted search.
- How do I handle breaking changes (e.g., new fields like `minHitCount`) in future updates?
- The bundle’s dynamic field system should minimize breakage, but always review the [changelog](https://sitepark.github.io/atoolo-docs/develop/bundles/graphql-search/changelog/). For Laravel, use schema migrations to update your GraphQL server’s configuration. Test thoroughly in staging before deploying to production.
- Does this bundle support spatial queries (e.g., geosearch) in Laravel?
- Yes, but your search backend must support it. Atoolo’s bundle includes spatial query syntax, so if you’re using Scout with a geospatial driver (e.g., PostgreSQL) or Algolia’s geosearch, it will work. Configure the backend to expose these features via Atoolo’s query DSL, then map them in your Laravel GraphQL resolvers.
- Who maintains Laravel-specific support for this Symfony bundle?
- The bundle is Symfony-focused, so Laravel-specific issues may not be prioritized. Engage with the [GitHub issues](https://github.com/sitepark/atoolo-graphql-search-bundle/issues) or fork the bundle to add Laravel wrappers. For critical projects, consider contributing adapters for Scout/Algolia or maintaining a separate Laravel package.