chore: Refactor the StorageExplorerStore to use API calls from the data folder
#23222
Conversation
This file contains 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
|
No changes detected in Branching Preview Branches by Supabase. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
6 Ignored Deployments
|
ivasilov
force-pushed
the
chore/storage-api-in-store
branch
from
b0b18f7
to
fe9cb27
Compare
alaister
reviewed
May 2, 2024
Comment on lines
+33
to
+37
| export function useBucketObjectDeleteMutation() { | ||
| return useMutation({ | ||
| mutationFn: deleteBucketObject, | ||
| }) | ||
| } |
There was a problem hiding this comment.
For all these new mutation functions is there a reason why we're not passing through the options like in the other mutations? Makes it easy to pass onSuccess() from outside for example
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.
No description provided.