[9.x] Vendor publish flag that restricts to only existing files #43212
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.
I often find myself overriding a specific view file for a vendor package and then losing track of whether the package eventually updated that file or not. While I could simply run
php artisan vendor:publish --tag=filament-config --force
, that publishes ALL of the view files when I am only interested in files that I have created manually. Since many packages have dozens, if not hundreds, of view files - this can be burdensome.This PR introduces a new
--existing
flag that instructs thevendor:publish
command to only publish and overwrite files that already exist.I did consider naming the flag
--force-only-existing
, or some variation thereof and would be open to any change you felt would be more appropriate.