📎 Implement lint/useNumberNamespace - eslint-unicorn/prefer-number-properties

[Conaclos]

Description

Implement prefer-number-properties

Biome already provides noGlovalIsFinite and noGlobalIsNan because the global and Number-namespaced functions have not the same semantic. Thus, the new rule should ignore these two functions.

The new rule could provide a safe fix.

Want to contribute? Lets you know you are interested! We will assign you to the issue to prevent several people to work on the same issue. Don't worry, we can unassign you later if you are no longer interested in the issue! Read our contributing guide and analyzer contributing guide.

Suggested names: useNumberNamespace, useNumberProperties

Implementation notes

Take a look at the implementations of noGlovalIsFinite and noGlobalIsNan.

[seitarof]

Hi! I'd like to try on this.

[ematipico]

I wonder why this should fail

const {parseInt} = Number;
const foo = parseInt('10', 2);

[Conaclos]

I wonder why this should fail

const {parseInt} = Number;
const foo = parseInt('10', 2);

Same here. I think we should only take global references into account. This example should pass.