Skip to content

errors: alter ERR_INVALID_DOMAIN_NAME#19961

Closed
davidmarkclements wants to merge 1 commit into
nodejs:masterfrom
davidmarkclements:error-patch6
Closed

errors: alter ERR_INVALID_DOMAIN_NAME#19961
davidmarkclements wants to merge 1 commit into
nodejs:masterfrom
davidmarkclements:error-patch6

Conversation

@davidmarkclements

@davidmarkclements davidmarkclements commented Apr 12, 2018

Copy link
Copy Markdown
Member

changes the base instance for ERR_INVALID_DOMAIN_NAME
from Error to TypeError as a more accurate representation
of the error.

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

@nodejs-github-bot nodejs-github-bot added the errors Issues and PRs related to JavaScript errors originated in Node.js core. label Apr 12, 2018
@vsemozhetbyt

Copy link
Copy Markdown
Contributor

Additionally corrects the grammar of the error message.

Seems obsolete?)

@vsemozhetbyt vsemozhetbyt added the http Issues or PRs related to the http subsystem. label Apr 12, 2018
changes the base instance for ERR_INVALID_DOMAIN_NAME
from Error to TypeError as a more accurate representation
of the error.
@davidmarkclements

Copy link
Copy Markdown
Member Author

@vsemozhetbyt it is - now removed from commit message

@jasnell

jasnell commented Apr 14, 2018

Copy link
Copy Markdown
Member

@BridgeAR BridgeAR added the semver-major PRs that contain breaking changes and should be released in the next major version. label Apr 15, 2018
@BridgeAR BridgeAR requested a review from a team April 15, 2018 21:49
@BridgeAR BridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Apr 15, 2018
@lpinca

lpinca commented Apr 16, 2018

Copy link
Copy Markdown
Member

This needs at least one more TSC approval before it can land.

@lpinca

lpinca commented Apr 16, 2018

Copy link
Copy Markdown
Member

cc: @nodejs/tsc

@mcollina mcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lpinca

lpinca commented Apr 16, 2018

Copy link
Copy Markdown
Member

Landed in 345e3b2.

@lpinca lpinca closed this Apr 16, 2018
lpinca pushed a commit that referenced this pull request Apr 16, 2018
Changes the base instance for ERR_INVALID_DOMAIN_NAME from Error to
TypeError as a more accurate representation of the error.

PR-URL: #19961
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
jasnell pushed a commit that referenced this pull request Apr 16, 2018
Changes the base instance for ERR_INVALID_DOMAIN_NAME from Error to
TypeError as a more accurate representation of the error.

PR-URL: #19961
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. errors Issues and PRs related to JavaScript errors originated in Node.js core. http Issues or PRs related to the http 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.

8 participants