Skip to content
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

feat: use url encoding type for list calls #14010

Merged

Conversation

pranavosu
Copy link
Member

@pranavosu pranavosu commented Nov 13, 2024

Description of changes

  • Set encoding type to url for list requests.
  • Decode output values.
  • Added unit tests

Issue #, if available

Description of how you validated changes

Checklist

  • PR description included
  • yarn test passes
  • Unit Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

Checklist for repo maintainers

  • Verify E2E tests for existing workflows are working as expected or add E2E tests for newly added workflows
  • New source file paths included in this PR have been added to CODEOWNERS, if appropriate

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

const decodeEncodedElements = (
listOutput: ListObjectsV2Output,
): ListObjectsV2Output => {
if (listOutput.EncodingType !== 'url') {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be not url if we are the ones setting this in first place?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's highly unlikely, but I'd rather be safe.

@pranavosu pranavosu changed the title feat: allow setting encoding type for list calls feat: use url encoding type for list calls Nov 14, 2024
Copy link
Member

@AllanZhengYP AllanZhengYP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@pranavosu pranavosu merged commit d8c0a68 into storage-browser/integrity Nov 14, 2024
28 checks passed
@pranavosu pranavosu deleted the storage-browser/handle-special-characters branch November 14, 2024 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants