9
10 return(
11 filtro?.map((item) => (
12 <div className='item' key={parseInt(item.objectID)}>13 <Book item = {item} />
14 </div>
15 )) 1import './style.css';
2const Book = (props) => {
3 return (
4 <div className='item' key={parseInt(props.item?.objectID)}> 5 <h2>{props.item?.title}</h2>
6 <h3> {props.item?.author || 'Sem Autor'} </h3>
7 <h3><a href={props.item?.url || ''}> {'Saiba Mais' || 'Sem Link'} </a></h3>When using the parseInt() function it is common to omit the second argument, the radix, and let the function try to determine from the first argument what type of number it is.
By default, parseInt() will autodetect decimal and hexadecimal (via 0x prefix).
Prior to ECMAScript 5, parseInt() also autodetected octal literals, which caused problems because many developers assumed a leading 0 would be ignored.
This confusion led to the suggestion that you always use the radix parameter to parseInt() to eliminate unintended consequences. So instead of doing this:
let num = parseInt("071"); // 57
Do this:
let num = parseInt("071", 10); // 71
ECMAScript 5 changed the behavior of parseInt() so that it no longer autodetects octal literals and instead treats them as decimal literals.
However, the differences between hexadecimal and decimal interpretation of the first parameter causes many developers to continue using the radix parameter to ensure the string is interpreted in the intended way.
On the other hand, if the code is targeting only ES5-compliant environments passing the radix 10 may be redundant.
In such a case you might want to disallow using such a radix.
Bad Practice
let num = parseInt("071");
num = parseInt(someValue);
num = parseInt("071", "abc");
num = parseInt();
Recommended
let num = parseInt("071", 10);
num = parseInt("071", 8);
num = parseFloat(someValue);