# javascript – JSLint says “missing radix parameter”

## The Question :

578 people think this question is useful

I ran JSLint on this JavaScript code and it said:

Problem at line 32 character 30: Missing radix parameter.

This is the code in question:

imageIndex = parseInt(id.substring(id.length - 1))-1;



What is wrong here?

1035 people think this answer is useful

It always a good practice to pass radix with parseInt –

parseInt(string, radix)



For decimal –

parseInt(id.substring(id.length - 1), 10)



If the radix parameter is omitted, JavaScript assumes the following:

• If the string begins with “0x”, the radix is 16 (hexadecimal)
• If the string begins with “0”, the radix is 8 (octal). This feature is deprecated
• If the string begins with any other value, the radix is 10 (decimal)

96 people think this answer is useful

To avoid this warning, instead of using:

parseInt("999", 10);



You may replace it by:

Number("999");



Note that parseInt and Number have different behaviors, but in some cases, one can replace the other.

44 people think this answer is useful

I’m not properly answering the question but, I think it makes sense to clear why we should specify the radix.

On MDN documentation we can read that:

If radix is undefined or 0 (or absent), JavaScript assumes the following:

• […]
• If the input string begins with “0”, radix is eight (octal) or 10 (decimal). Exactly which radix is chosen is implementation-dependent. ECMAScript 5 specifies that 10 (decimal) is used, but not all browsers support this yet. For this reason always specify a radix when using parseInt.
• […]

Source: MDN parseInt()

28 people think this answer is useful

You can turn off this rule if you wish to skip that test.

Insert:

radix: false



Under the “rules” property in the tslint.json file.

It’s not recommended to do that if you don’t understand this exception.

22 people think this answer is useful

Adding the following on top of your JS file will tell JSHint to supress the radix warning:

/*jshint -W065 */



5 people think this answer is useful

I solved it with just using the +foo, to convert the string.

Keep in mind it’s not great for readability (dirty fix).

console.log( +'1' )
// 1 (int)



3 people think this answer is useful

You can also simply add this line right above your parseInt line:

// eslint-disable-next-line



This will disable eslint check for the next line. Use this if you only need to skip one or two lines.

3 people think this answer is useful

Prior to ECMAScript 5, parseInt() also autodetected octal literals, which caused problems because many developers assumed a leading 0 would be ignored.

var num = parseInt("071");      // 57



Do this:

var num = parseInt("071", 10);  // 71

var num = parseInt("071", 8);

var num = parseFloat(someValue);



Reference

2 people think this answer is useful

Just put an empty string in the radix place, because parseInt() take two arguments:

string The value to parse. If the string argument is not a string, then it is converted to a string (using the ToString abstract operation). Leading whitespace in the string argument is ignored.

radix An integer between 2 and 36 that represents the radix (the base in mathematical numeral systems) of the above-mentioned string. Specify 10 for the decimal numeral system commonly used by humans. Always specify this parameter to eliminate reader confusion and to guarantee predictable behavior. Different implementations produce different results when a radix is not specified, usually defaulting the value to 10.

imageIndex = parseInt(id.substring(id.length – 1))-1;
imageIndex = parseInt(id.substring(id.length - 1), '')-1;

2 people think this answer is useful

Simply add your custom rule in .eslintrc which looks like that "radix": "off" and you will be free of this eslint unnesesery warning. This is for the eslint linter.

Instead of calling the substring function you could use .slice()
    imageIndex = parseInt(id.slice(-1)) - 1;