Closed benjam-es closed 2 years ago
I'm open to this.
Note: in the future if you already have code, just open the PR. No need for the issue, then the PR.
Noted.
Sorry, just created issues as an idea comes to mind. Been binge watching some of the blueprint videos since I came across it.
Synopsis:
It looks like the current method of publishing the 'stubs' files, is to use
php artisan vendor:publish --tag=...
which is usable. I think there may be room for improvement. Similarly it might be useful to complete multiple steps in one line (new, publish stubs, publish config)Proposed Syntax:
Use a new command for config publishing, which then simply calls the vendor:publish
php artisan blueprint:stubs
The
blueprint:new
command could have a couple of flags like so:blueprint:new --config
blueprint:new --stubs
blueprint:new --cs
(or shorthand)Expected Behavior: