Update: add fixer for prefer-numeric-literals

[not-an-aardvark]

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[x] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

Please check each item to ensure your pull request is ready:

• I've read the pull request guide
• I've included tests for my change
• I've updated documentation for my change (if appropriate)

What changes did you make? (Give an overview)

This adds a fixer for prefer-numeric-literals.

When given a function call such as parseInt('123', 16), the fixer replaces it with 0x123.

parseInt has some weird behavior; it accepts strings that look invalid. For example, parseInt('1 foo bar baz', 16) returns 1. The fixer only performs a fix if the literal in parseInt() would also be parseable as a regular number literal.

Is there anything you'd like reviewers to focus on?

Nothing in particular.

[mention-bot]

@not-an-aardvark, thanks for your PR! By analyzing the annotation information on this pull request, we identified @azhang496 to be a potential reviewer

[eslintbot]

LGTM

[platinumazure]

Just one question about the very last invalid test-- it looks like an unquoted string is used for parseInt, is that just a rendering issue on GitHub?

[not-an-aardvark]

I think it's just a rendering issue -- it looks fine for me. (screenshot)

[platinumazure]

LGTM

[platinumazure]

Ah, when I highlighted individual characters I eventually saw the quotes. Firefox rendering issue indeed, thanks.

[mysticatea]

LGTM, thank you!

[platinumazure]

I'll champion this one-- just need one more endorsement to accept.