linter: bunch of small auto-fix missing

[Hideman42]

What version of Oxlint are you using?

0.16.5

What command did you run?

oxlint --fix --fix-suggestions --quiet

What happened?

Missing lot of quick auto-fixes:

• eslint-plugin-unicorn(prefer-number-properties): Use Number.parseFloat instead of the global parseFloat => Same for parseInt, isNaN feat(linter): implement fixer for unicorn/prefer-number-properties #10693
  • Should add Number. before parseFloat
• eslint(radix): Missing radix parameter feat(linter): add auto-fix for eslint/radix #10652
  • Should add , 10 in the code as Number.parseInt(str, 10)
• eslint-plugin-unicorn(prefer-spread): Prefer the spread operator (...) over Array.from()
  • Should replace Array.from(store.getItems()) with [...store.getItems()] feat(linter): add fixer to unicorn/prefer-spread #10691
  • Should replace store.getItems()?.concat(anotherItem) ?? [anotherItem] with [...store.getItems() ?? [], anotherItem] // More complex
• eslint-plugin-react(jsx-curly-brace-presence): Curly braces are unnecessary here
  • Should replace <div id={'my-div'} /> with <div id="my-div" />
• eslint(require-await): Async function has no 'await' expression
  • Should strip out async // Maybe a dangerous fix
• eslint-plugin-react(self-closing-comp): Unnecessary closing tag
  • Should replace to self closing tag
• eslint-plugin-react(jsx-no-useless-fragment): Fragments should contain more than one child. feat(linter): implement suggestion for jsx/no-useless-fragment #10800
  • Should replace to <></> with null <>{something}</> with something
• eslint(eqeqeq): Expected === and instead saw ==
  • Should replace == to === feat(linter): allow eqeqeq to always be dangerously fixable #10499
• eslint-plugin-react(exhaustive-deps): React Hook useMyHook has a missing dependency myDep
  • Should add to the dependencies array myDep

[Dunqing]

Thank you for such a useful issue to help us improve!

[Miodec]

Just a heads up (since you mentioned youre using --fix and --fix-suggestions flags), eqeqeq should be a dangerous fix since just blindly changing == to === can change the logic.

[Hideman42]

Just a heads up (since you mentioned youre using --fix and --fix-suggestions flags), eqeqeq should be a dangerous fix since just blindly changing == to === can change the logic.

I think this is fair to have it as dangerous fix. Something is weird tho, I went to the rules doc and it is tagged as auto-fixable (safe) and I checked the rule source it seem to have a fix implemented but with oxlint --fix --fix-suggestions --fix-dangerously --quiet it doesnt auto fix it. Do you also confirm in your try?

[camchenry]

@Hideman42 I'll take a look at this. I think it is only safely auto fixable in some cases. But we could provide it as a dangerous fix in all cases.