-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
[Transforms] Merge master 06/06/2016 #8991
Conversation
@@ -28,12 +28,17 @@ namespace ts { | |||
const previousOnSubstituteNode = context.onSubstituteNode; | |||
context.onSubstituteNode = onSubstituteNode; | |||
context.enableSubstitution(SyntaxKind.Identifier); | |||
context.enableSubstitution(SyntaxKind.BinaryExpression); | |||
context.enableSubstitution(SyntaxKind.PrefixUnaryExpression); | |||
context.enableSubstitution(SyntaxKind.PostfixUnaryExpression); |
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.
You need to enable emit notification for source files so that you know the current source file during substitution.
… methods # Conflicts: # tests/cases/unittests/transpile.ts
(commandLineOptions_stringToEnum would be undefined if optionDeclarations wasn't loaded yet)
…n_clause minor fix: add missing return clause
…er-independent Primitive type guards are order independent
Current following tests are failing:
|
const sourceFileName = sourceFile ? sourceFile.fileName : undefined; | ||
if (bindingNameExportSpecifiers && bindingNameExportSpecifiers[sourceFileName] && hasProperty(bindingNameExportSpecifiers[sourceFileName], left.text)) { | ||
if (bindingNameExportSpecifiersForFileMap && | ||
bindingNameExportSpecifiersForFileMap[currentSourceFileIdDuringSubstitution] && |
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.
Can we store the result of this lookup in a local variable so we aren't performing the same lookup twice in a row?
After you address this comment (and the related comments), 👍 |
No description provided.