[4.x] Flush entire static_cache
cache store when running static:clear
#9770
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 pull request changes how we clear Static Caching related items from the Laravel cache.
Previously, when the static cache was cleared (either via
php please static:clear
or other means), we looped through thenocache::urls
and cleared the regions from the cache.This makes sense if we're using the "default" cache store. However, #9405 introduces a new, dedicated
static_cache
cache store for all things static caching related.So, instead of us just clearing the keys we can find, this pull request changes our approach to flush the entire
static_cache
cache store.If the application doesn't have a
static_cache
cache store, then it'll fallback to the previous implementation.Fixes #9765.