[8.x] Add optional 'exclude' parameter to the PruneCommand #39749
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.
This PR adds an optional 'exclude' parameter to the
Illuminate\Database\Console\PruneCommand
in order to exclude certain models that were automatically detected within the application'sapp\Models
directory.Of course, you could argue to remove the
Illuminate\Database\Eloquent\Prunable
orIlluminate\Database\Eloquent\MassPrunable
trait from those models.But what if you have a base class within the application's
app\Models
directory, which is implemented by other models and implements one of the above traits?That base class will not be able to return an
\Illuminate\Database\Eloquent\Builder
instance, as it does not have a corresponding database table.Looking forward to any feedback and suggestions regarding this PR.
Thanks!