feat: add clearCache() to purge cache without sending a request - #17
Merged
Sammyjo20 merged 2 commits intoSep 18, 2026
Merged
Conversation
Adds a deleteCache() method to the HasCaching trait that allows deleting a cached response without going through the middleware pipeline. Useful for applications that only want to delete the cache without immediately retrieving fresh data.
Sammyjo20
approved these changes
Sep 18, 2026
Sammyjo20
left a comment
Member
There was a problem hiding this comment.
Thanks @jornicornelese - great idea! I've tweaked the implementation a little bit and I've renamed it to clearCache.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Currently,
invalidateCache()only takes effect insideCacheMiddleware, meaning the cache is only refreshed when a request is actually sent. There's no way to just delete a cached response without making an API call.In my own application I ran into redundant API calls — I only wanted to invalidate the cache, not immediately retrieve fresh data. This PR adds a
deleteCache()method to theHasCachingtrait that deletes the cached response directly, without going through the middleware pipeline.Usage
Changes
deleteCache(Connector|Request $counterpart)toHasCachingCacheMiddleware(including customcacheKey()overrides)Driver::delete()directly — no existing code modified