-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
querystring: Parse multiple separator characters #3807
Closed
Closed
Conversation
This file contains 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
@@ -0,0 +1,23 @@ | |||
'use strict'; | |||
const assert = require('assert'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please require('../common');
LGTM with a few small comments. |
mscdex
added
the
querystring
Issues and PRs related to the built-in querystring module.
label
Nov 13, 2015
LGTM |
1 similar comment
LGTM |
yosuke-furukawa
force-pushed
the
yosuke-patch-1
branch
from
November 13, 2015 17:55
4e3ea02
to
f8a0443
Compare
yosuke-furukawa
added a commit
that referenced
this pull request
Nov 13, 2015
Fix querystring.parse to handle multiple separator characters PR-URL: #3807 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
Landed in a776a86 |
yosuke-furukawa
added a commit
that referenced
this pull request
Nov 17, 2015
Fix querystring.parse to handle multiple separator characters PR-URL: #3807 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
yosuke-furukawa
added a commit
that referenced
this pull request
Nov 30, 2015
Fix querystring.parse to handle multiple separator characters PR-URL: #3807 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
yosuke-furukawa
added a commit
that referenced
this pull request
Dec 4, 2015
Fix querystring.parse to handle multiple separator characters PR-URL: #3807 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
Closed
yosuke-furukawa
added a commit
that referenced
this pull request
Dec 17, 2015
Fix querystring.parse to handle multiple separator characters PR-URL: #3807 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
yosuke-furukawa
added a commit
that referenced
this pull request
Dec 23, 2015
Fix querystring.parse to handle multiple separator characters PR-URL: #3807 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
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.
When I explained
querystring
API for node beginners, I found a weird problem.I expect
{foo: 'bar', bar: 'baz'}
but the actual result is{foo: '>bar', bar: '>baz'}
.This PR solves the problem.