New
Introducing React Bench, see how different models perform on React code

react-doctor/prefer-es6-class

Use one component style consistently: ES2015 `class extends React.Component` (default) over the legacy `createReactClass` factory.

Status
Active
Category
Architecture
Assessment
Evidence-required risk
Required evidence
source code, repository context
Default configuration
Disabled until configured
Default severity
warn
Show technical metadata
Scope
All supported frameworks
Active when
always
Requirements
react
Priority
15 (P3)
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

In its default "always" mode, fires on any CallExpression whose callee is createReactClass(...) or React.createReactClass(...): the legacy ES5 component factory. Under the opt-in "never" mode it flips to flag class X extends Component | PureComponent | React.Component | React.PureComponent instead.

Suppress when: matching is purely syntactic on the callee name, so a same-named local helper called createReactClass that has nothing to do with React's factory is still flagged; confirm the call actually resolves to the react-create-class package before acting.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

  • Confirmed failure: The required evidence establishes the violation.
  • Rejected: A documented exception or false-positive predicate applies.
  • Needs evidence: Named evidence can still be collected.
  • Unavailable: Required evidence cannot be collected in this run.
  • Waived with evidence: An authorized, scoped exception applies to an established failure.
  • Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Convert the createReactClass({ render() {...} }) call into an ES2015 class: class Hello extends React.Component { render() { return <div>Hello {this.props.name}</div>; } }, moving displayName to a static field and lifecycle/render methods onto the class. Better still in modern React, rewrite as a function component if the class holds no state or lifecycle logic. See https://oxc.rs/docs/guide/usage/linter/rules/react/prefer-es6-class

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

Show repository-wide prompt

Fix every confirmed react-doctor/prefer-es6-class diagnostic in the current repository.

Required change:

  • Convert the createReactClass({ render() {...} }) call into an ES2015 class: class Hello extends React.Component { render() { return <div>Hello {this.props.name}</div>; } }, moving displayName to a static field and lifecycle/render methods onto the class. Better still in modern React, rewrite as a function component if the class holds no state or lifecycle logic. See https://oxc.rs/docs/guide/usage/linter/rules/react/prefer-es6-class.

Validation before editing:

In its default "always" mode, fires on any CallExpression whose callee is createReactClass(...) or React.createReactClass(...): the legacy ES5 component factory. Under the opt-in "never" mode it flips to flag class X extends Component | PureComponent | React.Component | React.PureComponent instead.

Suppress when: matching is purely syntactic on the callee name, so a same-named local helper called createReactClass that has nothing to do with React's factory is still flagged; confirm the call actually resolves to the react-create-class package before acting.

Constraints:

  • Make the smallest change that fixes the root cause.
  • Preserve behavior and interfaces unrelated to this diagnostic.
  • Reuse existing project components, utilities, and conventions.
  • Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
  • Adapt identifiers and framework details instead of copying blindly.
  • Do not disable the rule or suppress matching code.

Assessment:

  • Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
  • Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
  • A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:

  • Run focused tests for the changed behavior.
  • Run React Doctor and confirm this diagnostic no longer appears from changed code.
  • Run an unfiltered scan of the affected scope before claiming no cross-category regression.
  • Report the files changed and any checks you could not run.