Add an option for "new-parens" to require having no parenthesis on new

[pfgithub]

#10074 <!--
ESLint adheres to the JS Foundation Code of Conduct.

This template is for requesting a rule change. If you are here for another reason, please see below:

1. To report a bug: https://eslint.org/docs/developer-guide/contributing/reporting-bugs
2. To propose a new rule: https://eslint.org/docs/developer-guide/contributing/new-rules
3. To request a change that is not a bug fix, rule change, or new rule: https://eslint.org/docs/developer-guide/contributing/changes
4. If you have any questions, please stop by our chatroom: https://gitter.im/eslint/eslint

Note that leaving sections blank will make it difficult for us to troubleshoot and we may have to close the issue.

-->

What rule do you want to change?

new-parens

Does this change cause the rule to produce more or fewer warnings?

No

How will the change be implemented? (New option, new default behavior, etc.)?

Adds an option for always requiring or always not allowing new parens

Please provide some example code that this change will affect:

"new-parens": ["error", "never"]
Examples of incorrect code for this rule:

var person = new Person();
var person = new (Person)();
var thing = new Person().Thing

Examples of correct code for this rule:

var person = new Person;
var person = new (Person);
var person = new Person("Name");
var thing = (new Person).Thing

"new-parens": ["error", "always"]
Examples of incorrect code for this rule:

var person = new Person;
var person = new (Person);
var thing = (new Person).Thing;

Examples of correct code for this rule:

var person = new Person();
var person = new (Person)();
var person = new Person("Name");
var thing = new Person().Thing;

What does the rule currently do for this code?

Has no option of setting to require no parenthesis on new with no arguments

What will the rule do after it's changed?

Same thing as it currently does, but also includes an option to require no parenthesis on new constructors with no arguments

[not-an-aardvark]

Thanks for the proposal. How would the rule handle cases like this when using the never option?

new Foo().Bar

[pfgithub]

Thanks for the proposal. How would the rule handle cases like this when using the never option?

new Foo().Bar

This would be a warning/error. If --fix is applied it would surround it in parenthesis like (new Foo).Bar

[eslint-deprecated]

Unfortunately, it looks like there wasn't enough interest from the team
or community to implement this change. While we wish we'd be able to
accommodate everyone's requests, we do need to prioritize. We've found
that issues failing to reach accepted status after 21 days tend to
never be accepted, and as such, we close those issues.
This doesn't mean the idea isn't interesting or useful, just that it's
not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.