- Can I use gbenitez/attribute-bundle in a Laravel application?
- Not directly. It is a Symfony bundle that registers through config/bundles.php and expects Symfony's container, routing, form and translator services, none of which Laravel provides. Making it work would mean forking it or writing a compatibility shim, and even then you would be pulling Doctrine ORM and Twig into a Laravel app. There is no service provider or Illuminate integration in the package.
- Is gbenitez/attribute-bundle a PHP 8 attribute metadata library?
- No, despite the name. The v3.0.0 release clarifies that it is an EAV-style attribute CRUD application: it manages domain attribute entities with JSON column types, a Twig and Bootstrap 5 admin UI, Doctrine migrations and CSRF-protected deletes. It is not tooling for declaring or resolving PHP 8 attributes on classes and methods. If you want reflection-based metadata, this is the wrong package.
- What dependencies does gbenitez/attribute-bundle require?
- The release notes describe a Symfony surface built on Doctrine ORM with JSON column types, Twig 3.0 or newer, Symfony Form with OptionsResolver, Symfony routing and TranslatorInterface. Whether doctrine/orm, symfony/form and twig/twig are hard requirements or optional has not been confirmed in the available documentation. Inspect composer.json before assuming you can install a subset.
- How do I install gbenitez/attribute-bundle?
- Install it with Composer, register the bundle in config/bundles.php, then run the shipped Doctrine migrations to create its tables. The repository now includes INSTALLATION.md, TROUBLESHOOTING.md and a documented migration path from v2.x. You also need Doctrine, Twig and Symfony Form configured in the host application before the CRUD routes and admin UI will function.
- Which Symfony and PHP versions does gbenitez/attribute-bundle support?
- The package claims Symfony 5.4 LTS, 6.x and 7.x on PHP 7.4 through 8.3. The release notes only cite testing on Symfony 5.4 LTS and 6.1, so the wider matrix appears asserted rather than demonstrated. There is no confirmed CI configuration covering the full combination, and Symfony 6.1 is itself long past end of life.
- What are the alternatives to gbenitez/attribute-bundle for Laravel developers?
- For metadata on classes and methods, native PHP 8 attributes plus reflection are usually enough and need no package. For structured data objects and validation you can look at Laravel-oriented tools such as spatie/laravel-data, and for EAV-style characteristics a small Eloquent model with JSON columns will fit Laravel far better than a Symfony bundle. Evaluate these against your own requirements rather than assuming any single package maps to your domain.
- Does gbenitez/attribute-bundle work with Laravel 10 or Laravel 11 on PHP 8.2?
- The PHP floor of 7.4 does not conflict with Laravel 10 or 11, which run on PHP 8.1 and 8.2, so a Composer constraint collision is unlikely to be the blocker. The problem is coexistence: the package expects Doctrine, Twig and Symfony Form at runtime, so compatible PHP versions do not make it usable inside Laravel. Treat it as a separate Symfony application rather than a drop-in library.
- How do I test gbenitez/attribute-bundle?
- The repository ships a phpunit.xml.dist, which is a real improvement over earlier versions that had no visible test surface. However, it is unclear whether an actual CI pipeline runs the claimed Symfony 5.4, 6.x and 7.x by PHP 7.4 to 8.3 matrix, or whether compatibility is inferred from a single tested pair. Run the suite locally against your target Symfony and PHP versions before trusting any compatibility claim.
- Is v3.0.0 a breaking change and how hard is the migration?
- Yes, v3.0.0 is a major release with a documented migration path from v2.x. Adopting at a breaking-change boundary means any fork or shim you write starts from an unstable base, and the published roadmap to v3.1, v3.2 and v4.0 for Symfony 8 signals more majors ahead. Budget for repeated upgrade work if you commit to it.
- Is gbenitez/attribute-bundle production-ready and actively maintained?
- It is a single-maintainer package with no known dependents and no reported production usage, so the bus factor is one. Documentation has improved with INSTALLATION.md, TROUBLESHOOTING.md and an updated README, and a forward roadmap is published, which are positive signals. The licence is not stated in the available overview, so verify it in composer.json, and confirm the EAV data model matches a real need in your domain before adopting.