-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
[FrameworkBundle] Add --exclude option to the cache:pool:clear command
#51058
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
a9a13cc to
5126d11
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could also be done by not adding it to $pools and $clearers in the loop before instead of this unset solution, but fine for me this way.
Needs a related doc PR to explain the feature in docs.
5126d11 to
39fe666
Compare
|
Please always rebase, we don't accept PRs with merge commits in their history. |
b3312ea to
fa93e0c
Compare
|
Sorry, tried to rebase using GitHub UI but it ended in a merge commit 😅 |
|
We could deprecate |
To me this could be done in a separate PR, while this has some implicit drawbacks IMHO, because you could clear more than expected 👎 I would go with this PR as is |
fa93e0c to
21d0348
Compare
|
One last proposal from a DX perspective could be to give autocompletion for the possible values? |
|
Thank you @MatTheCat. |
…option (MatTheCat) This PR was squashed before being merged into the 6.4 branch. Discussion ---------- [Cache] Document `cache:pool:clear`’s new `--exclude` option Feature PR * symfony/symfony#51058 Commits ------- cc7ac50 [Cache] Document `cache:pool:clear`’s new `--exclude` option
For now this PR just ignores excluded pools/clearers when they don’t exist or wouldn’t be cleared/run anyways. Not sure what the best DX would be 🤔