maxmustermann/TypeScript
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Changed how parserContextFlags are handled in tests

Browse source
This commit is contained in:
Bill Ticehurst 2016-03-01 10:36:37 -08:00
parent ae27b89847
commit b5da80202f
2 changed files with 4 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/harness/harness.ts
View file

@ -285,6 +285,10 @@ namespace Utils {
// data we don't care about in the dump. We only care what the parser set directly
// on the ast.
let value = n.parserContextFlags & ts.ParserContextFlags.ParserGeneratedFlags;
// Remove the JavaScriptFile flag, as this is just noise for JSDocParser and Test262 tests
// (which are the only tests that use this function).
value = value & ~ts.ParserContextFlags.JavaScriptFile;
if (value) {
o[propertyName] = getParserContextFlagName(value);
}

5
tests/cases/unittests/jsDocParsing.ts
View file

@ -12,8 +12,6 @@ module ts {
let result = Utils.sourceFileToJSON(typeAndDiagnostics.jsDocTypeExpression.type);
// Remove the parserContextFlags from the comparison
result = result.replace(/\,\n\s+\"parserContextFlags\": \"JavaScriptFile\"/g, "");
assert.equal(result, expected);
}
@ -1002,9 +1000,6 @@ module ts {
: v;
}, 4);
// Remove the parserContextFlags from the comparison
result = result.replace(/\,\n\s+\"parserContextFlags\": \"JavaScriptFile\"/g, "");
if (result !== expected) {
// Turn on a human-readable diff
if (typeof require !== 'undefined') {