fix(es5): fix parseInt and parseFloat input type

[rafikalid]

Fix parseInt and parseFloat input type issue
issues
#50828
#17203
#38471

[typescript-bot]

It looks like you've sent a pull request to update our 'lib' files. These files aren't meant to be edited by hand, as they consist of last-known good states of the compiler and are generated from 'src/lib' or possibly our lib generator. Unless this is necessary, consider closing the pull request and sending a separate PR to update 'src/lib' or https://github.com/microsoft/TypeScript-DOM-lib-generator

[typescript-bot]

This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise.

[fatcerberus]

This almost certainly won’t be accepted. Note #17203 is tagged working as intended (and for good reason).

[rafikalid]

This almost certainly won’t be accepted. Note #17203 is tagged working as intended (and for good reason).

When I need to convert a number into an integer, I use this :
const myInteger= parseInt(542.33)
the same If I want to convert a big Integer into int.
I don't have a reason why limit this to string when to real API allows any type of data?

[XieJiSS]

I don't have a reason why limit this to string when to real API allows any type of data?

IMO TypeScript prevents people from doing dumb things, e.g. use parseInt to remove fraction part from a number

[MartinJohns]

I don't have a reason why limit this to string when to real API allows any type of data?

The real API also allows to pass objects and arrays.

[RyanCavanaugh]

The current behavior is intentional.