Enhancing Blueprint for Easier Domain-Driven Design Configuration

[eclipse313]

Description

I try to structure my project according to Domain-Driven Design principles. Specifically, I want my models and controllers to be placed in the appropriate domain-specific directories more easily. Below is an example of my draft.yml configuration:

models:
  NameOfDomain\Models\NameOfModel:
    name: string

controllers:
  # ...

In my config/blueprint.php, I have set the following:

'namespace' => 'App\\Domains',

'models_namespace' => '',
'controllers_namespace' => '',

This setup works as expected—models and controllers are correctly placed in the appropriate directories under app/Domains/. However, configuring the paths and namespaces manually in the draft.yml file feels cumbersome.

Expected Behavior

I would like a simpler way to configure Blueprint so that files are automatically generated under the appropriate domain-specific directories (e.g., app/Domains/NameOfDomain/Models/NameOfModel.php) without having to explicitly define the full namespace path in draft.yml.

Current Behavior

Currently, I have to explicitly define the full namespace path in the draft.yml file for each model or controller, which can be tedious for larger projects with multiple domains.

Steps to Reproduce

1. Configure Blueprint with the above config/blueprint.php settings and a draft.yml file as shown.
2. Run php artisan blueprint:build.
3. Check the generated files in app/Domains.

Possible Solution

Could there be an enhancement to Blueprint to support a simpler configuration for Domain-Driven Design projects? For example:

Allow defining a base domain or namespace in config.php or draft.yml - or one draft.yml file per domain?

Automatically infer the directory structure based on the domain and type of resource (e.g., models or controllers).

This would reduce the need for repetitive configuration in draft.yml and make it easier to generate files in a clean Domain-Driven Design structure.

Thank you for providing this tool—it’s been very helpful so far!

[jasonmccreary]

There was a PR (#543) where config can be added directly to the draft.yaml file. Maybe this would be valuable. If so, you are welcome to revive it.

I believe it was pretty close. It just needed a better description and code styling.

[eclipse313]

Thank you for the information. I think I'll make a pull request for the docs and document the info better there.

Unfortunately, I still don't quite understand how I should do this if I have more than one domain. How would I do it then: with several yaml files or do I really need one file per domain?

Thank you!