- Is petkopara/crud-generator-bundle a Laravel package?
- No. It is a Symfony bundle built for Symfony 3 and Doctrine entities, with no Laravel service provider, Artisan command, or laravel/framework constraint. Installing it in a Laravel application will not give you a working CRUD generator, and any generated code will target Symfony conventions rather than Eloquent and Blade.
- Can I install petkopara/crud-generator-bundle in a Laravel application?
- You can add it to composer.json, but it will not integrate: there is no service provider, no package auto-discovery, and no Artisan commands. The generated output assumes Doctrine ORM, Twig, Symfony annotations, SensioFrameworkExtraBundle, and Bootstrap 3.3.6. Treat installation into Laravel as unsupported and expect broken generated code.
- What does the CRUD generator actually generate from a Doctrine entity?
- It scaffolds a CRUD controller, form types, route definitions, and Twig templates from Doctrine entity metadata using a command-line generator. The generated views include pagination, column sorting, filtering, and bulk actions with Bootstrap-friendly markup. Once the files are emitted, the bundle's runtime role is effectively finished.
- Can I customize the templates used by the CRUD generator?
- Yes, the bundle ships customizable templates so generated views can be adjusted to match an application's markup and styling. In practice you would override Twig templates for a Symfony project, not Blade templates in Laravel. If your goal is a Laravel look and feel, porting the template structure into Blade is the real work.
- Does it work with Laravel Eloquent or only Doctrine ORM?
- Only Doctrine. The generator reads Doctrine entity metadata and emits Doctrine-backed controllers and repositories, so Eloquent models have no meaning to it. To reuse the ideas in Laravel you would need to rewrite generation around Eloquent query scopes, resource controllers, and Form Requests.
- Which Symfony and PHP versions does petkopara/crud-generator-bundle support?
- It targets Symfony 3-era projects and was last updated in March 2017, before PHP 7.4 typed properties and PHP 8 attributes. Expect deprecation warnings and outright failures on PHP 8.2 and later. Symfony 3.4 reached end of life in November 2021, so there is no supported upgrade path.
- Is petkopara/crud-generator-bundle maintained or abandoned?
- It is abandoned: the last release was on 2017-03-12 and there are zero dependents creating pressure to fix issues. No security response path exists for the bundle or for code it generates. The MIT license means you can fork and port it, but you own all maintenance from that point.
- What production risks come from code generated by this bundle?
- The main exposure is the generated code, not the library itself: N+1 query patterns, filter parameters applied without whitelisting, and bulk actions executed synchronously in the request cycle. Those become your production defects, and the MIT license gives no recourse. Generated markup also targets Bootstrap 3.3.6, which is long end-of-life.
- What are the best alternatives for Laravel CRUD scaffolding?
- For Laravel, Filament, Laravel Nova, Backpack, and InfyOm's generator are stronger on framework fit, maintenance, and security support. Below roughly ten entities or screens, hand-writing CRUD is often cheaper than adopting any generator. If you want this bundle's ideas, use it as a specification and reimplement its filter, pagination, and bulk-action patterns in Laravel.
- How should I test CRUD code generated from this bundle?
- Treat generated controllers as untrusted code and write feature tests for index filters, sorting, pagination boundaries, and bulk actions. Test against a copy of realistic data because filter parameters are applied without whitelisting and bulk actions run synchronously. If you run a Symfony sidecar, pin Symfony and PHP versions explicitly, since no upstream fixes will arrive.