[1.2] Refactoring stubs

[jaspertey]

Changes in #69 require stubs to be refactored before 1.2 can be officially tagged and released.

• Normalize stubs to use .stub extension instead of .php.stub (following Laravel's convention)
• Deprecate the ddd-specific model stub, now that ddd:model extends laravel's make:model and therefore inherits the native stubs.
• Breaking: change the location of where ddd stubs are published. They will now be published to base_path('stubs/ddd') instead of resource_path('stubs/ddd'). In other words, the ddd stubs will now be co-located alongside the framework's published stubs, within a ddd subfolder.
• For ddd:* generators that extend Laravel's make:* equivalent, custom stubs will be resolved as follows:
  • Try stubs/ddd/*.stub (allows customizing stub for ddd only)
  • Try stubs/*.stub (shared by both make:* and ddd:*)
  • Fallback to the framework default

Todo

• Implement ddd:publish to provide a more intuitive way to publish stubs selectively. Currently, to customize a ddd:model stub, you would have to publish all of laravel's stubs and customize the model.stub file, or make a copy of it into the ddd subfolder. The ideal workflow would be a way to publish ONLY the stub you need, and have it end up in stubs/ddd/*.stub automatically.

[npldevfr]

Hi, do you have an approximate release date for version 1.2? :)

[jaspertey]

Hi, do you have an approximate release date for version 1.2? :)

Hey Nathan, sorry for the delay and thanks for your patience! If you're not too concerned about potential issues with stubs, you can start using 1.2 like this:

composer require lunarstorm/laravel-ddd:dev-next 

You might have to set composer.json's minimum-stability to "beta"

I dropped the v1.2.0 pre-release recently, https://github.com/lunarstorm/laravel-ddd/releases/tag/v1.2.0-beta.1 - what is the composer convention to use pre-releases? I wasn't sure. Either way, targeting dev-next will work, as I'm pushing all progress to the next branch.