Weave Code
Ddd Generator Bundle Laravel Package
becklyn/ddd-generator-bundle
Symfony bundle to generate DDD boilerplate via Maker commands. Installs as a dev dependency and provides abstract makers (DddMaker, entity/test/command variants) plus templating support so you can create and register custom generators.
Code generator for common Domain Driven Design patterns in the Becklyn DDD framework.
Frequently asked questions about Ddd Generator Bundle
- Can I use becklyn/ddd-generator-bundle directly in a Laravel project?
- No, this package is designed for Symfony and requires Symfony’s Console, Dependency Injection, and templating systems. Laravel projects would need adapters (e.g., Symfony Console Bridge, custom DI bindings) or a hybrid approach to integrate it. Consider Laravel-native alternatives like `laravel-shift/ddd-framework` for seamless compatibility.
- What Laravel-specific DDD features does this bundle lack?
- It doesn’t support Eloquent models, Laravel migrations, or testing tools like Pest or Laravel’s `actingAs()` helpers. Generated commands won’t register natively with Artisan, requiring manual overrides. Symfony’s `CommandBus` and `EventDispatcher` won’t integrate without additional work.
- How do I install this bundle in a Laravel project?
- Run `composer require becklyn/ddd-generator-bundle --dev`, but note this is a Symfony bundle. You’ll need to manually register it in `config/bundles.php` (Symfony-only) and handle conflicts with Laravel’s service container. Test in a non-production environment first due to potential runtime errors.
- Are there alternatives for Laravel DDD code generation?
- Yes. For Laravel, consider `laravel-shift/ddd-framework` (native Eloquent support), `spatie/laravel-model-generator` (simpler boilerplate), or custom Artisan commands using Laravel’s `make:command` and `make:model`. These avoid Symfony dependencies entirely.
- Can I extend the bundle’s makers (e.g., DddEntityMaker) for custom generators?
- Yes, but you’ll need to adapt the Symfony-specific logic. Extend `DddMaker`, `DddEntityMaker`, or their test/command variants, then register your service with the `maker.command` tag. Templates use `.tpl.php` files (Symfony’s `PhpEngine`), which won’t work natively in Laravel without a templating adapter.
- Will this bundle work with Laravel 10+ and Symfony 6+?
- The bundle supports Symfony 6, but Laravel’s incompatibility with Symfony’s Console and DI systems means it won’t integrate out-of-the-box. Test thoroughly for breaking changes, especially if using Symfony services like `CommandBus`. Laravel’s container won’t autowire Symfony services by default.
- How do I handle template rendering in Laravel if I use this bundle?
- The bundle uses Symfony’s `.tpl.php` templating, which Laravel doesn’t support. You’d need to either: 1) Pre-process templates outside Laravel, 2) Fork the bundle to replace `PhpEngine` with Laravel’s Blade or native PHP templating, or 3) Use a separate Symfony micro-service to generate files.
- Does this bundle support testing frameworks like Pest or PHPUnit in Laravel?
- No. Generated test classes (e.g., via `DddEntityTestMaker`) won’t integrate with Laravel’s testing helpers like `actingAs()` or `refreshDatabase()`. You’d need to manually adapt test files or use Laravel’s native testing tools to mock the generated DDD components.
- What’s the maintenance overhead for using this in Laravel?
- High. You’ll need to maintain custom adapters for Symfony’s Console, DI, and templating systems. Future Symfony updates may break compatibility, and the bundle’s last release in 2022 suggests limited long-term support. Weigh this against Laravel-native solutions.
- Can I run Symfony commands from Laravel to use this bundle?
- Yes, as a workaround: Use Laravel’s `Process` facade to execute Symfony commands in a separate process. For example, run `php bin/console ddd:generate` from an Artisan command. This isolates Symfony dependencies but adds complexity to file handling and error management.
Weaver
How can I help you explore Laravel packages today?