docs(linter): Mark some react rules as unsupported, misc docs improvements

[connorshea]

Marks the following rules from eslint-plugin-react as unsupported:

• react/default-props-match-prop-types
• react/forbid-foreign-prop-types
• react/forbid-prop-types
• react/no-access-state-in-setstate
• react/no-unused-class-component-methods
• react/no-unused-state
• react/no-unused-prop-types
• react/prefer-exact-props
• react/sort-comp
• react/sort-default-props
• react/sort-prop-types
• react/static-property-placement

I also considered adding react/require-optimization to the unsupported list, but there's an open PR for it right now, so I'll leave it be.

These rules are not necessary to support, as React 19 and/or TypeScript have basically eliminated their usefulness entirely. Some are also arguably stylistic.

See https://react.dev/blog/2024/04/25/react-19-upgrade-guide#removed-proptypes-and-defaultprops for notes on the defaultProps/propTypes removal.

Basically, modern React for >7 years has been primarily about function components

createReactClass has been removed entirely from React core, it was moved into a separate package:

var Component = createReactClass({
  propTypes: {
    a: PropTypes.any,
    r: PropTypes.array,
    o: PropTypes.object
  },
...
});

Class-based components are discouraged and marked as legacy in the React docs

class Greeting extends Component {
  render() {
    return <h1>Hello, {this.props.name}!</h1>;
  }
}

And these rules mostly - or exclusively - cover behaviors relating to these older component patterns.

I'm actually curious to hear @baevm's opinion on dropping these as rules we want to add support for, in case he has any opinion on the matter.

[Copilot]

Pull request overview

This PR marks 10 React rules from eslint-plugin-react as unsupported in oxlint, based on the rationale that React 19 and TypeScript have made them obsolete. The rules primarily apply to legacy class components, PropTypes, and defaultProps - patterns that are discouraged in modern React development.

Changes:

• Added 10 React rules to the unsupported rules list with explanations
• Enhanced documentation for no_string_refs rule with React 19 removal information
• Added TypeScript-specific note to jsx_no_undef rule documentation

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
tasks/lint_rules/src/unsupported-rules.json	Adds 10 React rules to unsupported list with rationale explaining their obsolescence in modern React
crates/oxc_linter/src/rules/react/no_string_refs.rs	Updates documentation to clarify deprecation timeline and React 19 removal of string refs
crates/oxc_linter/src/rules/react/jsx_no_undef.rs	Adds note about rule being unnecessary when using TypeScript

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[camc314]

@connorshea I'll leave this for you to merge in case you want to wait for @ baevm to review

[camc314]

@connorshea I'll leave this for you to merge in case you want to wait for @ baevm to review

[baevm]

i think its fine, there is also no-typos rule only for class components/prop types and no-arrow-function-lifecycle for class components, maybe also add it?

[connorshea]

I'm going to merge this as-is for now since I have to wake up early tomorrow, if anyone wants to follow up with those two extra rules feel free :)

[connorshea]

Merge activity

• Jan 27, 6:19 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jan 27, 6:19 AM UTC: connorshea added this pull request to the Graphite merge queue.
• Jan 27, 6:26 AM UTC: Merged by the Graphite merge queue.