-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
test: add two test cases for querystring #11481
Conversation
I think just using 'test' for the subsystem in the first line of the commit is enough, as no change to the actual |
Ahh ok, now the tagging rule becomes apparent to me. Thanks! |
+ Check an empty substring: In `querystring`, if the `maxKeys` is 1 and the state machine finds an empty substring between separators, it should return an empty object. + Test invalid encoded strings: If provided string is an invalid encoded string in `query.parse`, it will not be encoded.
ca83f15
to
6913df6
Compare
+ Check an empty substring: In `querystring`, if the `maxKeys` is 1 and the state machine finds an empty substring between separators, it should return an empty object. + Test invalid encoded strings: If provided string is an invalid encoded string in `query.parse`, it will not be encoded. PR-URL: #11481 Reviewed-By: Timothy Gu <timothygu99@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
@addaleax ... just fyi, I was landing this PR just as your review came in so you're not listed on the reviewers |
Landed in dd2e135 |
@jasnell guess what I was just going to push to master! 😄 |
not landing in |
Should this be backported to v6.x-staging? If yes please follow the guide and raise a backport PR, if no let me know or add the |
Since this update was related to the breaking change of the querystring in v8.x, I replaced |
This test will improve
querystring
coverage:The following lines will be called with the cases:
node/lib/querystring.js
Line 332 in 88035bc
node/lib/querystring.js
Line 399 in 88035bc
Checklist
make -j4 test
Affected core subsystem(s)
test