Closed innoflash closed 4 years ago
Hey, looks like these are going to add great functionality to packer. I will check and if everything works fine, I will merge it soon.
Thanks for your contribution.
Hey, looks like these are going to add great functionality to packer. I will check and if everything works fine, I will merge it soon.
Thanks for your contribution.
All good, but i wasn`t sure about the command names so you might wanna change them to fit your naming conventions
When creating a certain package i realized there are some provider types that we could have been missing. Here is what i could compile:
When registering policies in the Laravel default app you place your gates in the
App\Providers\AuthServiceProvider
which imports a certain type of provider to achieve that => solvedpackr make:auth-provider {ProviderName}
When making Laravel events and listeners you will have to register them in the
App\Providers\EventServiceProvider
which also imports another ServiceProvider with event handling abilities => solvedpackr make:event-provider {ProviderName}
Perhaps you would want to do customized
route model binding
, apart from using thebindings
middleware to your routes, you will need to override it inApp\Providers\RouteServiceProvider
in default Laravel so we have to make that possible within our packages => solvedpackr make:route-provider {ProviderName}
Lastly if we need to activate broadcasts in our package will have to do it in our
App\Providers\BroadcastServiceProvider
which is a Laravel default but we should be able to create our own in our package and modify it => solvedpackr make:broadcast-provider {ProviderName}
This is basically it, the current defauit
ServiceProvider
can do all other jobs but misses the above mentionedCheers