More human-friendly autofix variables

[blackswanny]

When rule applied during autofix, it extracts inline code into variables usually by adding underscore prefix to avoid duplicates, for instance _onClick, __onClick, ___onClick.
We suggest to add different human-friendly approach, since underscore is not common in Javascript naming.
For instance, camelCase with number in the end:

onClickOne
onClickTwo
onClickThree

or ideally with semantic context reading some sibling attributes, properties, which is harder to implement

onClickSubmit
onClickApply

[blackswanny]

I added PR for this
#54

[arthurgeron]

The idea behind placing a uncomfortable underscore is specifically so that devs know these variables were created by the auto-fix and that they need a proper name. Identifying \s[_]{1,}[a-z]{1,} is much easier than something lexical like one, two three, which is almost impossible to find.

Different than the other fixes, I never intended for the auto-created variables to be used as is, since imho it's essential that even the simplest variables/methods have a proper name, e.g. handleCreateUser for ex it's much better than just _onClick or `onClickOne when you many onClicks in the same file.

[blackswanny]

So, the reason for this request is because those underscore variables still slip into commits, as developer trust autofix eslint rules and any changes it makes, because that's perception of any eslint rule that is auto fixable. So in my experience they won't be looking for underscore variables to fix them.
I understand word-numbers is not much better than underscore, but it at least complies with common naming
If not number, there could be other solution, whatever variables can be found in scope, I assume getVariableInScope gives more semantic options to try. Most buttons, inputs have name, label and other common attributes making them good candidates for proper naming

[arthurgeron]

I understand the necessity here, but I'm not fond of officially adopting a specific approach and then perhaps finding edge cases or not being the best solution for everyone.

The best solution here would be to accept a custom method for generating variable names via options. What do you think?

I'd be happy to accept a contribution towards that generic approach. Then you'd be able to use your own preferred algorithm at your projects.