some error message text additions #11
Merged
Conversation
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
| ✔️ Deploy Preview for netlify-plugin-cloudinary ready! 🔨 Explore the source changes: 1905b87 🔍 Inspect the deploy log: https://app.netlify.com/sites/netlify-plugin-cloudinary/deploys/6206e2e23045a10008a70f0d 😎 Browse the preview: https://deploy-preview-11--netlify-plugin-cloudinary.netlify.app/ |
| thanks @Chuloo! |
| @all-contributors please add @Chuloo for code |
| I've put up a pull request to add @Chuloo! 🎉 |
colbyfayock pushed a commit that referenced this pull request Oct 19, 2022
# Description Logo images in README change dynamically, adapting to the user's theme ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #38 ## 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 - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock pushed a commit that referenced this pull request Oct 21, 2022
# Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Aug 29, 2023
# Description The build plugin currently primarily utilizes the `DEPLOY_PRIME_URL` environment variable to determine the Netlify host for building URLs specifically with the Fetch API. The issues is that in production context, this URL will still prepend the branch (like "main") instead of the primary Netlify host. This checks the deploy context and if its production, uses the `NETLIFY_HOST` variable which includes that primary host. ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #45 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Aug 29, 2023
# Description The NETLIFY_HOST as fixed in #47 only captured 1 instance where it was used in 2 different locations. This fixes the second location ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #45 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Aug 31, 2023
# Description For each image, attempt to look up if that image has a preload tag associated with it and replace the URL of that tag to avoid duplicate image requests. Active use case is Next.js App Router with the Next Image component. ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #54 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Sep 7, 2023
# Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Sep 15, 2023
# Description Adds the ability to enable Private CDN or specify a custom CNAME for Advanced Plan users. ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #51 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Sep 15, 2023
# Description This sets up the ability to allow for more than one path to be configured for images. Instead of only being able to: ``` imagesPath = "/my-path" ``` You can now add: ``` imagesPath = [ "/my-path", "/my-other-path" ] ``` ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #61 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Sep 19, 2023
# Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #80 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Sep 19, 2023
# Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #83 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Sep 20, 2023
# Description Allows the ability to pass in the maxSize option where you can configure a maximum width and height to use for images. Images will automatically resize down to the maximum values preserving the aspect ratio. It will also not upscale, only downscale. ``` [plugins.inputs.maxSize] width = 1200 height = 800 ``` ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #62 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
some error message text additions
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
…ary-community#38) (cloudinary-community#39) # Description Logo images in README change dynamically, adapting to the user's theme ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes cloudinary-community#38 ## 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 - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# Description The build plugin currently primarily utilizes the `DEPLOY_PRIME_URL` environment variable to determine the Netlify host for building URLs specifically with the Fetch API. The issues is that in production context, this URL will still prepend the branch (like "main") instead of the primary Netlify host. This checks the deploy context and if its production, uses the `NETLIFY_HOST` variable which includes that primary host. ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes cloudinary-community#45 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# [1.5.0](cloudinary-community/netlify-plugin-cloudinary@v1.4.0...v1.5.0) (2023-08-29) ### Features * updating package-lock ([2a89820](cloudinary-community@2a89820)) * Use Netlify Host with Production Context ([cloudinary-community#47](cloudinary-community#47)) ([896bcda](cloudinary-community@896bcda)), closes [cloudinary-community#11](cloudinary-community#11) [cloudinary-community#45](cloudinary-community#45)
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# Description The NETLIFY_HOST as fixed in cloudinary-community#47 only captured 1 instance where it was used in 2 different locations. This fixes the second location ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes cloudinary-community#45 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
## [1.5.1](cloudinary-community/netlify-plugin-cloudinary@v1.5.0...v1.5.1) (2023-08-29) ### Bug Fixes * Fixes missing Netlify Host check ([cloudinary-community#50](cloudinary-community#50)) ([646e1f3](cloudinary-community@646e1f3)), closes [cloudinary-community#47](cloudinary-community#47) [cloudinary-community#11](cloudinary-community#11) [cloudinary-community#45](cloudinary-community#45)
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
…nary-community#55) # Description For each image, attempt to look up if that image has a preload tag associated with it and replace the URL of that tag to avoid duplicate image requests. Active use case is Next.js App Router with the Next Image component. ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes cloudinary-community#54 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# [1.6.0](cloudinary-community/netlify-plugin-cloudinary@v1.5.1...v1.6.0) (2023-08-31) ### Features * Replace preload tags for related image source if exists ([cloudinary-community#55](cloudinary-community#55)) ([aaa030f](cloudinary-community@aaa030f)), closes [cloudinary-community#11](cloudinary-community#11) [cloudinary-community#54](cloudinary-community#54)
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# Description Adds the ability to enable Private CDN or specify a custom CNAME for Advanced Plan users. ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes cloudinary-community#51 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# [1.9.0](cloudinary-community/netlify-plugin-cloudinary@v1.8.0...v1.9.0) (2023-09-15) ### Features * CNAME & Private CDN ([cloudinary-community#71](cloudinary-community#71)) ([17fff6b](cloudinary-community@17fff6b)), closes [cloudinary-community#11](cloudinary-community#11) [cloudinary-community#51](cloudinary-community#51)
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# Description This sets up the ability to allow for more than one path to be configured for images. Instead of only being able to: ``` imagesPath = "/my-path" ``` You can now add: ``` imagesPath = [ "/my-path", "/my-other-path" ] ``` ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes cloudinary-community#61 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# [1.10.0](cloudinary-community/netlify-plugin-cloudinary@v1.9.0...v1.10.0) (2023-09-15) ### Features * Configure Multiple Image Paths ([cloudinary-community#75](cloudinary-community#75)) ([e10cffa](cloudinary-community@e10cffa)), closes [cloudinary-community#11](cloudinary-community#11) [cloudinary-community#61](cloudinary-community#61)
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
…y-community#81) # Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes cloudinary-community#80 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
## [1.10.1](cloudinary-community/netlify-plugin-cloudinary@v1.10.0...v1.10.1) (2023-09-19) ### Bug Fixes * Fixes missing API Key and Secret failing Fetch builds ([cloudinary-community#81](cloudinary-community#81)) ([cdd5981](cloudinary-community@cdd5981)), closes [cloudinary-community#11](cloudinary-community#11) [cloudinary-community#80](cloudinary-community#80)
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes cloudinary-community#83 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
## [1.10.2](cloudinary-community/netlify-plugin-cloudinary@v1.10.1...v1.10.2) (2023-09-19) ### Bug Fixes * Fixes Netlify URL ([cloudinary-community#84](cloudinary-community#84)) ([3a83908](cloudinary-community@3a83908)), closes [cloudinary-community#11](cloudinary-community#11) [cloudinary-community#83](cloudinary-community#83)
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# Description Allows the ability to pass in the maxSize option where you can configure a maximum width and height to use for images. Images will automatically resize down to the maximum values preserving the aspect ratio. It will also not upscale, only downscale. ``` [plugins.inputs.maxSize] width = 1200 height = 800 ``` ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`cloudinary-community#11`) or issue URL. --> <!-- Example: Fixes cloudinary-community#1 --> Fixes cloudinary-community#62 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
matiasfha pushed a commit to matiasfha/netlify-plugin-cloudinary that referenced this pull request Sep 23, 2023
# [1.11.0](cloudinary-community/netlify-plugin-cloudinary@v1.10.2...v1.11.0) (2023-09-20) ### Features * Max Size ([cloudinary-community#78](cloudinary-community#78)) ([57cb8fb](cloudinary-community@57cb8fb)), closes [cloudinary-community#11](cloudinary-community#11) [cloudinary-community#62](cloudinary-community#62)
colbyfayock added a commit that referenced this pull request Nov 7, 2023
# Description Migrates from Jest to Vitest ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #90 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Nov 10, 2023
# Description Concurrency was added for parallel uploads which introduced a bug where the try/catch wrapping this didn't properly catch the errors being thrown from within the async functions. This moves the try/catch inside of each upload process ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #94 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
colbyfayock added a commit that referenced this pull request Feb 13, 2024
# Description Appends the analytics codes to the URL for internal analytics Currently this doesn't support SDK Semver or Tech Version due to being unable to get version imports working without having to manually configure it each time. will open a separate issue to address this ## Issue Ticket Number <!-- Specifiy which issue this fixes by referencing the issue number (`#11`) or issue URL. --> <!-- Example: Fixes #1 --> Fixes #70 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] 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. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/netlify-plugin-cloudinary/issues) ticket for this PR - [ ] 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? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
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.
Just added some more text to the error messages. Just me being picky, you can ignore too ;).
Asides this, I think everything else is great. Thanks for the plugin.