Upgrading

From 1.1.x to 1.2.x

Stubs are now published to base_path('stubs/ddd') instead of resource_path('stubs/ddd'). In other words, they are now co-located alongside the framework's published stubs, within a ddd subfolder.
Published stubs now use .stub extension instead of .php.stub (following Laravel's convention).
If you are using published stubs from pre 1.2, you will need to refactor your stubs accordingly.

Support for Application Layer and Custom Layers was added, introducing changes to the config file.
Run php artisan ddd:config update to rebuild your application's published ddd.php config to align with the package's latest copy.
The update utility will attempt to respect your existing customizations, but you should still review and verify manually.

Old way (removed): php artisan vendor:publish --tag="ddd-stubs"
New way: php artisan ddd:stub (see Customizing Stubs in README for more details).

Minimum required Laravel version is 10.25.
The ddd generator command syntax in 1.x. Generator commands no longer receive a domain argument. For example, instead of ddd:action Invoicing CreateInvoice, one of the following would be used:
- Using the --domain option: ddd:action CreateInvoice --domain=Invoicing (this takes precedence).
- Shorthand syntax: ddd:action Invoicing:CreateInvoice.
- Or simply ddd:action CreateInvoice to be prompted for the domain afterwards.
The config file was refactored. A helper command ddd:upgrade is available to assist with this, but it is strongly recommended that you simply wipe out the old config and re-publish via php artisan vendor:publish --tag="ddd-config" and re-configure accordingly.
If applicable, stubs should also be re-published via php artisan vendor:publish --tag="ddd-stubs" and re-customized as needed.
In production, ddd:cache should be run during the deployment process. See the Autoloading in Production section for more details.