Rule Change: overlapping "no-new-symbol" and "no-new-native-nonconstructor"

[danielrentz]

What rule do you want to change?

no-new-symbol, no-new-native-nonconstructor

What change to do you want to make?

Generate fewer warnings

How do you think the change should be implemented?

Other

Example code

const s = new Symbol();

What does the rule currently do for this code?

Both rules "no-new-symbol" and "no-new-native-nonconstructor" trigger.

What will the rule do after it's changed?

• "no-new-symbol" should be deprecated.
• "no-new-native-nonconstructor" should become recommended (as "no-new-symbol" was).

Participation

• I am willing to submit a pull request to implement this change.

Additional comments

No response

[snitin315]

Hi @danielrentz, Thanks for creating this issue. This was discussed in the PR and we decided not to deprecate the no-new-symbol as mentioned in #16368 (review)

in most cases we could deprecate a rule in a minor release, but we're unable to add no-new-native-nonconstructor to eslint:recommended until the next major release, so resolving the deprecation warning would require users to manually override eslint:recommended even if they previously had no customizations. I will, however, call out the replacement in the release notes.

[snitin315]

I would suggest you disable the "no-new-symbol" rule in favor of the no-new-native-nonconstructor rule

[danielrentz]

Thanks for the pointer, missed that