-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
url, test: fix typo in inspect output, add test #10231
Conversation
1802acb
to
ed7c570
Compare
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.
Awesome! This LGTM if CI is green and @jasnell and/or @joyeecheung are happy with it
Got a surprised ping here. Can I review this even if I am not a collaborator? |
@joyeecheung Don’t feel obligated to do anything here! It’s just that I’d feel more comfortable with somebody reviewing this who has a bit more experience with the And to answer your question, yes, you can – PRs still need to be approved by at least one collaborator, but that does not mean that input from others can’t just be as valuable. |
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.
LGTM with nits.
const v = line.slice(i + 2); | ||
if (keys.has(k)) { | ||
common.fail('duplicate key found: ' + k); | ||
} |
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.
Nits: Would you mind changing this to assert.strictEqual(keys.has(k), false, 'duplicate key found: ' + k)
? Just like what you did on L195.
ed7c570
to
cf1307f
Compare
@joyeecheung Good suggestion. I made the change, PTAL. |
One final thing: Could you wrap the commit message body at 72 columns? Otherwise this should be ready to land, and if you prefer, the person landing this can take care of that for you. |
In the string returned from URL.inspect there was an extra semicolon at the end when showHidden === true. The semicolon has been removed and a test for the inspect function has been added. The test parses the returned string, validates all of the contained keys/values and tests logic related to the showHidden option.
cf1307f
to
35fd1e6
Compare
Commit message fixed, wrapped at 72. |
Great, thanks! Landed in 4f97a14 🎉 |
In the string returned from URL.inspect there was an extra semicolon at the end when showHidden === true. The semicolon has been removed and a test for the inspect function has been added. The test parses the returned string, validates all of the contained keys/values and tests logic related to the showHidden option. PR-URL: nodejs#10231 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
In the string returned from URL.inspect there was an extra semicolon at the end when showHidden === true. The semicolon has been removed and a test for the inspect function has been added. The test parses the returned string, validates all of the contained keys/values and tests logic related to the showHidden option. PR-URL: #10231 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
Description of change
In the string returned from URL.inspect there was an extra semicolon
at the end when showHidden === true. The semicolon has been
removed and a test for the inspect function has been added. The test
parses the returned string, validates all of the contained keys/values
and tests logic related to the showHidden option.