-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
errors, path: migrate to use internal/errors.js #11319
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,7 +20,7 @@ | |
// USE OR OTHER DEALINGS IN THE SOFTWARE. | ||
|
||
'use strict'; | ||
require('../common'); | ||
const common = require('../common'); | ||
const assert = require('assert'); | ||
const path = require('path'); | ||
|
||
|
@@ -88,29 +88,21 @@ const unixSpecialCaseFormatTests = [ | |
[{}, ''] | ||
]; | ||
|
||
const expectedMessage = common.expectsError({ | ||
code: 'ERR_INVALID_ARG_TYPE', | ||
type: TypeError | ||
}); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ditto. |
||
|
||
const errors = [ | ||
{method: 'parse', input: [null], | ||
message: /^TypeError: Path must be a string\. Received null$/}, | ||
{method: 'parse', input: [{}], | ||
message: /^TypeError: Path must be a string\. Received {}$/}, | ||
{method: 'parse', input: [true], | ||
message: /^TypeError: Path must be a string\. Received true$/}, | ||
{method: 'parse', input: [1], | ||
message: /^TypeError: Path must be a string\. Received 1$/}, | ||
{method: 'parse', input: [], | ||
message: /^TypeError: Path must be a string\. Received undefined$/}, | ||
{method: 'format', input: [null], | ||
message: | ||
/^TypeError: Parameter "pathObject" must be an object, not object$/}, | ||
{method: 'format', input: [''], | ||
message: | ||
/^TypeError: Parameter "pathObject" must be an object, not string$/}, | ||
{method: 'format', input: [true], | ||
message: | ||
/^TypeError: Parameter "pathObject" must be an object, not boolean$/}, | ||
{method: 'format', input: [1], | ||
message: | ||
/^TypeError: Parameter "pathObject" must be an object, not number$/}, | ||
{method: 'parse', input: [null], message: expectedMessage}, | ||
{method: 'parse', input: [{}], message: expectedMessage}, | ||
{method: 'parse', input: [true], message: expectedMessage}, | ||
{method: 'parse', input: [1], message: expectedMessage}, | ||
{method: 'parse', input: [], message: expectedMessage}, | ||
{method: 'format', input: [null], message: expectedMessage}, | ||
{method: 'format', input: [''], message: expectedMessage}, | ||
{method: 'format', input: [true], message: expectedMessage}, | ||
{method: 'format', input: [1], message: expectedMessage}, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We'll need to agree on whether the tests should check the contents of the message or not, but since have landed tests both with and without, I'm fine with landing as is. |
||
]; | ||
|
||
checkParseFormat(path.win32, winPaths); | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -372,7 +372,7 @@ function fail(fn) { | |
|
||
assert.throws(() => { | ||
fn.apply(null, args); | ||
}, TypeError); | ||
}, common.expectsError({code: 'ERR_INVALID_ARG_TYPE', type: TypeError})); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Tritto |
||
} | ||
|
||
typeErrorTests.forEach((test) => { | ||
|
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.
Could you add an assertion on the message as well?
(Changing the message is
semver-major
so let's enforce it)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.
This is a semver-major change, so it's totally fine to change the message.
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.
Yes, but let's keep it from regressing.