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

Remove all uses of encodeURIcomponent #62

Closed
wants to merge 1 commit into from
Closed

Conversation

cdersky
Copy link

@cdersky cdersky commented May 9, 2016

encodeURIcomponent throws exceptions, so its replaced with queryString.escape. This change is made in parallel with issue #528 in IronMan-S3.

@LaurenSpiegel
Copy link
Contributor

We should add a test with one of the examples that throw in the JS docs.

@LaurenSpiegel
Copy link
Contributor

👍

  encodeURIcomponent throws exceptions, so its replaced with queryString.escape . One test added to verify that queryString.escape does not throw an error.
@rahulreddy
Copy link
Collaborator

Let' do an end-to-end test to ensure compatibility as MetaData uses bucketclient in its tests. I can create a temp. branch in MetaData and S3 to launch the test.

@ghost
Copy link

ghost commented May 9, 2016

querystring.escape() also throws.

https://github.com/nodejs/node/blob/v4.x/lib/querystring.js#L145

@rahulreddy
Copy link
Collaborator

Looks like they actually landed the commit in 4.x last week 😕
nodejs/node#3702

@rahulreddy
Copy link
Collaborator

Tests pass in 4.4.1 and fail in 4.4.4. I think they landed this change in 4.4.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants