Skip to content

fix: tap parser fails when test name includes non ASCII characters #45741

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.

Sign up for GitHub

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

Closed
pulkit-30 wants to merge 2 commits into from
Closed

fix: tap parser fails when test name includes non ASCII characters #45741

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b1fda06
fix: tap parser fails when test name includes non ASCII characters
pulkit-30 Dec 5, 2022
07a6ab7
replaced ascii.test method with RegExpPrototypeExec method
pulkit-30 Dec 5, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
replaced ascii.test method with RegExpPrototypeExec method
  • Loading branch information
@pulkit-30
pulkit-30 committed Dec 5, 2022
commit 07a6ab796e53464ed8d23634efbb5467a5664ae5
4 changes: 2 additions & 2 deletions lib/internal/test_runner/tap_lexer.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
'use strict';

const { SafeSet, MathMax, StringPrototypeIncludes } = primordials;
const { SafeSet, MathMax, StringPrototypeIncludes, RegExpPrototypeExec } = primordials;
const {
codes: { ERR_TAP_LEXER_ERROR },
} = require('internal/errors');
Expand Down Expand Up @@ -485,7 +485,7 @@ class TapLexer {

#isNonASCIISymbol(char) {
const ascii = /^[ -~]+$/;
return !ascii.test(char);
return RegExpPrototypeExec(ascii, char) === null;
}

#isWhitespaceSymbol(char) {
Expand Down