- Can I use ite/doctrine-extra-bundle in a Laravel application?
- Not directly as a dependency. It is a Symfony bundle that relies on Symfony bundle registration, a DependencyInjection extension with a config tree, compiler passes, and tagged services, none of which Laravel provides in its request lifecycle. Laravel does not use the Symfony Kernel bundle registry, so the package has no natural attachment point in a standard Laravel stack. Only its framework-agnostic leaf classes could be adapted by extraction.
- How do I install ite/doctrine-extra-bundle with Composer?
- You can require it with Composer using composer require ite/doctrine-extra-bundle. In Symfony you must also enable the bundle in bundles.php and configure its extension. In Laravel, installation alone will not wire any services or configuration because there is no Symfony bundle registration or config-tree compiler. Check the composer.json constraints for php, doctrine/orm, doctrine/dbal, and symfony/* before assuming it resolves with your lockfile.
- Does ite/doctrine-extra-bundle work with laravel-doctrine/orm?
- There is no natural integration between this Symfony bundle and laravel-doctrine/orm. Laravel Doctrine brings its own service provider and manager registry, but that is not a Symfony container, so the bundle's registrations, compiler passes, and tagged services will not be picked up. At best, you could lift individual DBAL types, filters, hydrators, or repository traits and re-register them yourself.
- What features does ite/doctrine-extra-bundle provide?
- It adds practical Doctrine ORM and DBAL extensions for Symfony applications. The stated features include repository helpers for filtering, sorting, and pagination, custom DBAL types and Doctrine extensions ready to register, query utilities that reduce boilerplate in DQL and QueryBuilder code, and sensible defaults with bundle configuration for per-project overrides. The value is concentrated in small utility classes rather than deep framework integration.
- Is ite/doctrine-extra-bundle maintained and safe for production?
- There is little evidence of maintenance or production use. The package has very low adoption, no visible dependents, and no known issue-response or release-cadence history, and it is a single-author package without community review. A code audit and supply-chain review would be required before adding it to a production dependency graph. Given the low adoption signal, it should not be adopted directly without a strong reason.
- What Laravel and PHP versions does ite/doctrine-extra-bundle support?
- Laravel version support is not applicable because this is a Symfony bundle rather than a Laravel package. PHP support depends on its composer.json constraints, which should be checked alongside doctrine/orm, doctrine/dbal, and symfony/* requirements. There is no confirmed Laravel compatibility, and you must verify whether its constraints resolve against your existing lockfile.
- How does ite/doctrine-extra-bundle compare to DoctrineExtensions or laravel-doctrine/extensions?
- It overlaps with maintained options such as DoctrineExtensions and laravel-doctrine/extensions in areas like custom DBAL types, filters, and query utilities. For a Laravel application using Doctrine, laravel-doctrine/extensions is the more natural integration point because it targets the Laravel Doctrine ecosystem rather than the Symfony container. If you use Eloquent, first-party casts and scopes may already cover many of the convenience features this bundle offers.
- Can I extract only the custom DBAL types or repository helpers without using Symfony?
- Possibly, but that is extraction rather than installation. The bundle is small, and its reusable value is likely concentrated in leaf classes such as custom DBAL types, ORM filters, hydrators, and repository traits, which are largely framework-agnostic. Everything around them, including registration, configuration, and compiler passes, is Symfony-specific and would need to be rewritten as a Laravel service provider. A timeboxed spike is the sensible way to quantify the actual behavior before committing.
- How do I test ite/doctrine-extra-bundle in a Laravel or Symfony app?
- In Symfony, you would enable the bundle in a test kernel and provide configuration for its extension. In Laravel, there is no Symfony bundle kernel, so meaningful tests would need to target extracted classes or a reimplementation registered through a Laravel service provider. There is no visibility in the provided context into test coverage or CI, so the repository should be audited before relying on it.
- What should I check before adding ite/doctrine-extra-bundle to composer.json?
- Check the composer.json constraints on php, doctrine/orm, doctrine/dbal, and symfony/* and confirm they resolve against your lockfile. Review license and provenance, the last 24 months of commit history, test coverage or CI, and any security disclosure channel. Also confirm the specific capability is not already covered by Eloquent, laravel-doctrine/extensions, DoctrineExtensions, or roughly 100 lines of your own code. Given the zero adoption signal, the safer path is to reject it as a dependency and treat it as a design reference.