Skip to content

Decode Public ID to avoid double encoding#60

Merged
colbyfayock merged 2 commits intomainfrom
bug/59-parse
Jul 17, 2023
Merged

Decode Public ID to avoid double encoding#60
colbyfayock merged 2 commits intomainfrom
bug/59-parse

Conversation

@colbyfayock
Copy link
Collaborator

Description

Decodes the Public ID to avoid double encoding after passing in to the URL Gen SDK, which encodes the value itself.

Issue Ticket Number

Fixes #59

Type of change

  • 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)
  • Fix or improve the documentation
  • This change requires a documentation update

Checklist

  • I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
  • I have created an issue ticket for this PR
  • I have checked to ensure there aren't other open Pull Requests 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

@vercel
Copy link

vercel bot commented Jul 17, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
cloudinary-util ❌ Failed (Inspect) Jul 17, 2023 4:35pm

@colbyfayock colbyfayock merged commit c4c6bad into main Jul 17, 2023
@colbyfayock colbyfayock deleted the bug/59-parse branch July 17, 2023 16:37
github-actions bot pushed a commit that referenced this pull request Jul 17, 2023
# [@cloudinary-util/url-loader-v3.9.1](https://github.com/colbyfayock/cloudinary-util/compare/@cloudinary-util/url-loader-v3.9.0...@cloudinary-util/url-loader-v3.9.1) (2023-07-17)

### Bug Fixes

* Decode Public ID to avoid double encoding ([#60](#60)) ([c4c6bad](c4c6bad)), closes [#59](#59)
@github-actions
Copy link

🎉 This PR is included in version @cloudinary-util/url-loader-v3.9.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this pull request Jul 17, 2023
# [@cloudinary-util/util-v2.2.1](https://github.com/colbyfayock/cloudinary-util/compare/@cloudinary-util/util-v2.2.0...@cloudinary-util/util-v2.2.1) (2023-07-17)

### Bug Fixes

* Decode Public ID to avoid double encoding ([#60](#60)) ([c4c6bad](c4c6bad)), closes [#59](#59)
@github-actions
Copy link

🎉 This PR is included in version @cloudinary-util/util-v2.2.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

colbyfayock added a commit to cloudinary-community/next-cloudinary that referenced this pull request Jul 18, 2023
# Description

- Fixes issue with double encoding
cloudinary-community/cloudinary-util#60

- Fixes issue where signature was not allowing special characters `-_`
cloudinary-community/cloudinary-util#61

## Issue Ticket Number

Fixes #219 

<!-- Specify above which issue this fixes by referencing the issue
number (`#<ISSUE_NUMBER>`) or issue URL. -->
<!-- Example: Fixes
https://github.com/colbyfayock/next-cloudinary/issues/<ISSUE_NUMBER> -->

## 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)
- [ ] Fix or improve the documentation
- [ ] 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/next-cloudinary/issues) ticket
for this PR
- [ ] I have checked to ensure there aren't other open [Pull
Requests](https://github.com/colbyfayock/next-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
lytro-dev pushed a commit to lytro-dev/next-image-delivery that referenced this pull request Dec 23, 2023
# Description

- Fixes issue with double encoding
cloudinary-community/cloudinary-util#60

- Fixes issue where signature was not allowing special characters `-_`
cloudinary-community/cloudinary-util#61

## Issue Ticket Number

Fixes #219 

<!-- Specify above which issue this fixes by referencing the issue
number (`#<ISSUE_NUMBER>`) or issue URL. -->
<!-- Example: Fixes
https://github.com/colbyfayock/next-cloudinary/issues/<ISSUE_NUMBER> -->

## 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)
- [ ] Fix or improve the documentation
- [ ] 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/next-cloudinary/issues) ticket
for this PR
- [ ] I have checked to ensure there aren't other open [Pull
Requests](https://github.com/colbyfayock/next-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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Public ID parsing error when using encoded value

1 participant