Call to Function object JS-R1003
Anti-pattern
5 months ago
—
5 months old
Call to
Function object 5729 }
5730 function f() {
5731 try {
5732 var t = Function("return this")().require("vertx"); 5733 return (U = t.runOnLoop || t.runOnContext), i();
5734 } catch (e) {
5735 return c();Call to
Function object 5941 else if ("undefined" != typeof self) t = self;
5942 else
5943 try {
5944 t = Function("return this")(); 5945 } catch (e) {
5946 throw new Error(
5947 "polyfill failed because global object is unavailable in this environment"Call to
Function object 6054 else if ("undefined" != typeof self) t = self;
6055 else
6056 try {
6057 t = Function("return this")(); 6058 } catch (e) {
6059 throw new Error(
6060 "polyfill failed because global object is unavailable in this environment"Call to
Function object 5842 }
5843 function f() {
5844 try {
5845 var t = Function("return this")().require("vertx"); 5846 return (U = t.runOnLoop || t.runOnContext), i();
5847 } catch (e) {
5848 return c();
Description
Creating functions using the Function constructor can be avoided when all arguments are strings.
JS runtimes find it easier to optimize functions that are written in plain JavaScript syntax.
Consider using arrow functions, or the function keyword instead.
Bad Practice
const add = new Function('a', 'b', 'return a + b')
const sub = Function('a', 'b', 'return a - b')
Recommended
const add = function (a, b) { return a + b }
const sub = function (a, b) { return a - b }