Typescript code would always have the LIMIT_NAVIGATION_GLOBAL_CHECK fail. This was happening because the atomic LIMIT_NAVIGATION_JS_CHECK was looking for an AST node of type Literal, instead of using AstHelper.StringLiteral. As a result, the check worked properly for javascript code but not typescript.
This PR:
fixes this particular issue
adds a test case
makes the coding style consistent across the CustomArgumentsJSCheck as well
Typescript code would always have the LIMIT_NAVIGATION_GLOBAL_CHECK fail. This was happening because the atomic LIMIT_NAVIGATION_JS_CHECK was looking for an AST node of type Literal, instead of using AstHelper.StringLiteral. As a result, the check worked properly for javascript code but not typescript.
This PR: