Is there a TypeScript rule called "no-function-constructor-with-string-args" that needs an example?

Question

The description provided at this link is concise:

Avoid using the Function constructor with a string argument to define the function body

This might also apply to the rule missing-optional-annotation:

A parameter that comes after one or more optional parameters is not marked as optional itself

Answer 1

Answer №1

An interesting scenario can be found in the testing suite for eslint, which showcases a common issue developers may encounter.

const example = new Function("doSomething()");

This usage would result in a violation of the rule prohibiting the use of the Function constructor with string arguments.

Another situation arises with the missing-optional-annotation rule, as illustrated below:

function sample(requiredParam1, optionalParam2?, requiredParam3) {}

In this case, while the second parameter is marked as optional, the third parameter is not, causing a violation to occur.

Answer 2

An interesting scenario can be found in the testing suite for eslint, which showcases a common issue developers may encounter.

const example = new Function("doSomething()");

This usage would result in a violation of the rule prohibiting the use of the Function constructor with string arguments.

Another situation arises with the missing-optional-annotation rule, as illustrated below:

function sample(requiredParam1, optionalParam2?, requiredParam3) {}

In this case, while the second parameter is marked as optional, the third parameter is not, causing a violation to occur.