prefer-numeric-literals
Disallow parseInt()
and Number.parseInt()
in favor of binary, octal, and hexadecimal literals
Some problems reported by this rule are automatically fixable by the --fix
command line option
This rule is currently frozen and is not accepting changes.
The parseInt()
and Number.parseInt()
functions can be used to turn binary, octal, and hexadecimal strings into integers. As binary, octal, and hexadecimal literals are supported in ES6, this rule encourages use of those numeric literals instead of parseInt()
or Number.parseInt()
.
0b111110111 === 503;
0o767 === 503;
Rule Details
This rule disallows calls to parseInt()
or Number.parseInt()
if called with two arguments: a string; and a radix option of 2 (binary), 8 (octal), or 16 (hexadecimal).
Examples of incorrect code for this rule:
/*eslint prefer-numeric-literals: "error"*/
=== 503;
=== 503;
=== 503;
=== 503;
=== 503;
=== 503;
=== 503;
Examples of correct code for this rule:
/*eslint prefer-numeric-literals: "error"*/
parseInt(1);
parseInt(1, 3);
Number.parseInt(1);
Number.parseInt(1, 3);
0b111110111 === 503;
0o767 === 503;
0x1F7 === 503;
a[parseInt](1,2);
parseInt(foo);
parseInt(foo, 2);
Number.parseInt(foo);
Number.parseInt(foo, 2);
When Not To Use It
If you want to allow use of parseInt()
or Number.parseInt()
for binary, octal, or hexadecimal integers, or if you are not using ES6 (because binary and octal literals are not supported in ES5 and below), you may wish to disable this rule.
Compatibility
- JSCS: requireNumericLiterals
Version
This rule was introduced in ESLint v3.5.0.