Add vendor:publish support #124
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It enables configuration files and other publishable assets from external composer dependencies to be published directly into a specific module.
This makes it easier to configure third-party packages used by individual modules without affecting the global application scope.
Example
When installing
lucasdotvin/laravel-soulbscription, we might want to publish its migration and configuration files inside theBillingmodule.However, the published configuration file is not automatically loaded.
To load it, we can manually merge the configuration in
BillingServiceProvider:This change simplifies that workflow by integrating
vendor:publishbehavior directly with the module system.