☂️ eslint-plugin-react-perf

[DonIsaac]

Warning

This comment is maintained by CI. Do not edit this comment directly.
To update comment template, see https://github.com/oxc-project/oxc/tree/main/tasks/lint_rules

This is the tracking issue for eslint-plugin-react-perf.

There are 4(+ 0 deprecated) rules.

• 0/3 recommended rules are remaining as TODO
  • All done! 🎉
• 0/1 not recommended rules are remaining as TODO
  • All done! 🎉

To get started, run the following command:

just new-react-perf-rule <RULE_NAME>

Then register the rule in crates/oxc_linter/src/rules.rs and also declare_all_lint_rules at the bottom.

Recommended rules

✅: 3, 🚫: 0, ⏳: 0 / total: 3

Status	Name
✅	react-perf/jsx-no-new-array-as-prop
✅	react-perf/jsx-no-new-function-as-prop
✅	react-perf/jsx-no-new-object-as-prop

✅ = Implemented, 🚫 = No need to implement, ⏳ = Fix pending

Not recommended rules

✅: 1, 🚫: 0, ⏳: 0 / total: 1

Status	Name
✅	react-perf/jsx-no-jsx-as-prop

✅ = Implemented, 🚫 = No need to implement, ⏳ = Fix pending

[Boshen]

Last task:

• add a cli flag --react-perf-plugin and change all the rules to correctness.

[daniilium]

How do these rules for Visual Studio Code extensions work? I'm using the oxlintrc.json configuration file.