Skip to content

Commit 0b3242c

Browse files
committed
assert: fix generatedMessage property
This makes sure the `generatedMessage` property is always set as expected. This was not the case some `assert.throws` and `assert.rejects` calls. PR-URL: #28263 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
1 parent ace3f16 commit 0b3242c

1 file changed

Lines changed: 10 additions & 3 deletions

File tree

‎lib/assert.js‎

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -571,14 +571,21 @@ function expectedException(actual, expected, message, fn) {
571571
if(expected.test(str))
572572
return;
573573

574-
thrownewAssertionError({
574+
if(!message){
575+
generatedMessage=true;
576+
message='The input did not match the regular expression '+
577+
`${inspect(expected)}. Input:\n\n${inspect(str)}\n`;
578+
}
579+
580+
consterr=newAssertionError({
575581
actual,
576582
expected,
577-
message: message||'The input did not match the regular expression '+
578-
`${inspect(expected)}. Input:\n\n${inspect(str)}\n`,
583+
message,
579584
operator: fn.name,
580585
stackStartFn: fn
581586
});
587+
err.generatedMessage=generatedMessage;
588+
throwerr;
582589
}
583590

584591
// Handle primitives properly.

0 commit comments

Comments
 (0)