[11.x] Allow exceptions to the optimize
and optimize:clear
commands
#54070
+78
−2
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.
Summary
This PR introduces the
--except
option to theoptimize
andoptimize:clear
commands, enabling greater flexibility in managing optimization tasks. This change allows developers to integrate with these commands while providing control over which specific tasks are executed or skipped.Use Case
In applications deployed on Laravel Vapor, route caching is unsupported. By leveraging the
--except
option, we can utilize theoptimize
command without triggering unsupported operations likeroute:cache
.Examples
New Help
Feedback
Welcome to input on strategy or additional use cases this feature could support.