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

dns: synchronize resolve() docs and code #13090

Closed
wants to merge 1 commit into from
Closed

Conversation

Trott
Copy link
Member

@Trott Trott commented May 18, 2017

Synchronize the argument list for dns.resolve() with what's in the
documentation.

Improve the error for a bad rrtype to be a TypeError rather than an
Error.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
Affected core subsystem(s)

dns

@Trott Trott added dns Issues and PRs related to the dns subsystem. dont-land-on-v4.x semver-major PRs that contain breaking changes and should be released in the next major version. labels May 18, 2017
@nodejs-github-bot nodejs-github-bot added the dns Issues and PRs related to the dns subsystem. label May 18, 2017
@Trott
Copy link
Member Author

Trott commented May 20, 2017

@Trott
Copy link
Member Author

Trott commented May 20, 2017

Sole test failure is an unrelated known flaky with a fix pending.

@Trott
Copy link
Member Author

Trott commented May 20, 2017

/ping @nodejs/ctc This is ready to land except that it needs another signoff from a CTC member because it is semver-major because of the change to the error message.

@silverwind
Copy link
Contributor

Can use a more descriptive commit title? I wouldn't know what this is about if it were in the changelog like it is.

@Trott
Copy link
Member Author

Trott commented May 28, 2017

Can use a more descriptive commit title? I wouldn't know what this is about if it were in the changelog like it is.

I'm open to suggestions that are less than 50 characters. :-D

@silverwind
Copy link
Contributor

silverwind commented May 28, 2017

49 chars: dns: Return TypeError on invalid resolve() input

Synchronize the argument list for `dns.resolve()` with what's in the
documentation.

Improve the error for a bad `rrtype` to be a `TypeError` rather than an
`Error`.
@Trott
Copy link
Member Author

Trott commented May 28, 2017

Rebased, updated commit message.

New CI: https://ci.nodejs.org/job/node-test-pull-request/8352/

@joaocgreis
Copy link
Member

node-test-commit-arm-fanned failed because of a worker issue, here is another run with the same parameters: https://ci.nodejs.org/job/node-test-commit-arm-fanned/9057/

@Trott Trott removed the ctc-review label May 29, 2017
Trott added a commit to Trott/io.js that referenced this pull request May 29, 2017
Synchronize the argument list for `dns.resolve()` with what's in the
documentation.

Improve the error for a bad `rrtype` to be a `TypeError` rather than an
`Error`.

PR-URL: nodejs#13090
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
@Trott
Copy link
Member Author

Trott commented May 29, 2017

Landed in 758a17f

@Trott Trott closed this May 29, 2017
@Trott
Copy link
Member Author

Trott commented May 29, 2017

It's fine if this has to wait for Node 9.0.0 to be released, but for the record, it is the tiniest of semver majors (change in type from Error to TypeError) and I wouldn't oppose it landing in Node 8.0.0 if it's not too late. Either way is fine with me. /cc @jasnell

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dns Issues and PRs related to the dns subsystem. semver-major PRs that contain breaking changes and should be released in the next major version.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants