laravel-beyond
laravel-beyond copied to clipboard
AkrilliA
Create Laravel classes in a domain driven way (insired by Spatie Laravel Beyond CRUD)
As https://github.com/regnerisch/laravel-beyond/issues/54 requested, I have created `beyond:make:trait` command. The trait is created in `Domain\XXX\Traits` namespace by default. You can add `--support` flag to create the trait in `Support\Packages\Laravel\Traits` namespace.
Maybe you should include a command like `php artisan beyond:make:trait Users/UserTypeTrait`. Which then would land with flags or so to support or in the domain. Default is it in domain...
I think it would be really helpful to document what each type of action which can be generated is good for.
Just like #37 based on Ryutu Hamasakis talk at Laracon Online Winter 2022 (https://youtu.be/0Rq-yHAwYjQ?t=5885 -> link now with different timestamp than before): To seperate the domain boundaries we could use...
- [x] Missing `beyond:make:migration` command - [x] The given module "Auth}" does not exists. Did you run `php artisan beyond:make:module Auth`? - [x] Module can not be `--force` overwritten -...
Hello, I don't like to put my tasks in the `app/Console/Kernel`. Do you have any idea where I could put it instead? Furthermore commands are not registered from modules (yet).