Laravel package for generating Laravel Modules from a template.
Laravel 8 or 9 and PHP 8.0
You can see a video demo on YouTube
You can install the package via composer:
composer require dcblogdev/laravel-module-generator
Publish both the config
and stubs
:
php artisan vendor:publish --provider="Dcblogdev\ModuleGenerator\ModuleGeneratorServiceProvider"
This will publish a generator.php
config file
This contains:
'path' => env('GENERATOR_PATH', 'stubs/module-generator'),
'ignore_files' => ['module.json']
By default, the stubs will be located at stubs/module-generator you can add your own paths by adding your paths to your .env file or changing the config file.
GENERATOR_PATH=your-location
Create or update the stubs file. The filename and contents should have placeholders for example ModulesController
will be replaced with your name + Controller. ie ContactsController
when the command is executed.
Placeholders:
These placeholders are replaced with the name provided when running php artisan module:build
Used in filenames:
Module
= Module name ie Contacts
module
= Module name in lowercase ie contacts
Model
= Model name ie Contact
model
= Model name in lowercase ie contact
For a folder called
Models
rename it toEntities
it will be renamed when back to Models when generating a new module.
Only used inside files:
{Module}
= Module name ie PurchaseOrders
{module}
= Module name in lowercase ie purchaseOrder
{module_}
= module name with underscores ie purchase_orders
{module-}
= module name with hyphens ie purchase-orders
{module }
= module name puts space between capital letters ie PurchaseOrders
becomes Purchase Orders
{Model}
= Model name ie PurchaseOrder
{model}
= Model name in lowercase ie purchaseOrder
{model_}
= model name with underscores ie purchase_orders
{model-}
= model name with hyphens ie purchase-orders
{model }
= model name puts space between capital letters ie PurchaseOrder
becomes Purchase Order
Please see the changelog for more information on what has changed recently.
Contributions are welcome and will be fully credited.
Contributions are accepted via Pull Requests on Github.
-
Document any change in behaviour - Make sure the
readme.md
and any other relevant documentation are kept up-to-date. -
Consider our release cycle - We try to follow SemVer v2.0.0. Randomly breaking public APIs is not an option.
-
One pull request per feature - If you want to do more than one thing, send multiple pull requests.
If you discover any security related issues, please email dave@dcblog.dev email instead of using the issue tracker.
license. Please see the license file for more information.