-
Notifications
You must be signed in to change notification settings - Fork 12.8k
No error on indirect calls #35878
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
No error on indirect calls #35878
Conversation
The TypeScript team hasn't accepted the linked issue #35866. If you can get it accepted, this PR will have a better chance of being reviewed. |
1 similar comment
The TypeScript team hasn't accepted the linked issue #35866. If you can get it accepted, this PR will have a better chance of being reviewed. |
Yes we have |
return node.kind === SyntaxKind.Identifier && (node as Identifier).escapedText === "eval"; | ||
function isInIndirectCall(node: BinaryExpression) { | ||
return node.parent.kind === SyntaxKind.ParenthesizedExpression && (isCallExpression(node.parent.parent) && node.parent.parent.expression === node.parent || node.parent.parent.kind === SyntaxKind.TaggedTemplateExpression) && | ||
(isAccessExpression(node.right) || isIdentifier(node.right) && node.right.escapedText === "eval"); |
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.
Why do we still have to check for eval
? I think we want to silence the error for any indirect calls.
@ajafff Do you still want to work on this? Otherwise I'd like to close it to reduce the number of open PRs. |
Closing since this has gotten stale. |
Fixes: #35866 (in case you want to accept that issue)
@RyanCavanaugh for review