-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
Allow deleting file that is already deleted in Cloudinary #8410
Conversation
Signed-off-by: Arnelle Balane <arnellebalane@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #8410 +/- ##
=======================================
Coverage 33.27% 33.27%
=======================================
Files 1220 1220
Lines 13625 13625
Branches 1357 1357
=======================================
Hits 4534 4534
Misses 8207 8207
Partials 884 884
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
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.
LGTM, Thanks for this improvement !
Signed-off-by: Arnelle Balane <arnellebalane@gmail.com> Signed-off-by: Raj Nandigalla <raj.nandigalla@ril.com>
Signed-off-by: Arnelle Balane <arnellebalane@gmail.com>
Signed-off-by: Arnelle Balane <arnellebalane@gmail.com>
What does it do?
Handle the case with strapi-provider-upload-cloudinary when trying to delete a file that is already deleted in Cloudinary. Cloudinary responds with
{ result: 'not found' }
when trying to delete a non-existent file. This is added as an extra condition to be checked in strapi-provider-upload-cloudinary before throwing an error.Why is it needed?
When using strapi-provider-upload-cloudinary and the file is already deleted in Cloudinary, that file cannot be deleted from the Strapi UI and throws an internal server error.
Related issue(s)/PR(s)
Fix #5729 Cannot delete file already deleted in Cloudinary