-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Test failure logging for uploads #58
Comments
@colbyfayock When you say
You mean checking if when it will be about to upload (here] Since it is a remote URL, halt/throw and log? |
@matiasfha no - the idea was to potentially lock down the allowed referrers of the asset so that when trying to download it its not allowed. idk if this would work in practice, but trying to think of ways that the uploader itself will throw the error as thats what we're trying to test |
# Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> Catch errors when using cloudinary uploader. Throw in the lib catch during build and log them . ## Issue Ticket Number Fixed #58  ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [X] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # Checklist <!-- These must all be followed and checked. --> - [X] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [X] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [X] I have checked to ensure there aren't other open [Pull Requests](https://github.com/colbyfayock/netlify-plugin-cloudinary/pulls) for the same update/change? - [X] I have performed a self-review of my own code - [X] I have run tests locally to ensure they all pass - [X] I have commented my code, particularly in hard-to-understand areas - [X] I have made corresponding changes needed to the documentation
🎉 This issue has been resolved in version 1.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Potential cases:
The text was updated successfully, but these errors were encountered: