feat(storage): expose purgeCache#1742
Open
mandarini wants to merge 1 commit into
Open
Conversation
Contributor
|
This PR has been marked as stale because it has not had activity for 90 days. Please rebase and update if this is still needed. |
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.
Authored by @mansueli
Moved from here: supabase/storage-js#229
What kind of change does this PR introduce?
The goal is to expose the purgeCache operation from the API to the client libraries.
What is the current behavior?
There's no support this in the client libraries.
What is the new behavior?
The goal is to allow this to be exposed in the supabase-js client e.g: