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

react-hooks-js/todo

Unimplemented features

Status
Active
Category
React Compiler
Assessment
Evidence-required risk
Required evidence
source code
Default severity
error
Show technical metadata
Scope
All supported frameworks
Active when
eslint-plugin-react-hooks v6+ installed AND React Compiler detected in project
Priority
24 (P3)
Source
eslint-plugin-react-hooks
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.

Hint-severity diagnostic the Compiler emits when it bails on a feature it should support but has not yet implemented: not a code mistake, more of a 'Compiler cannot optimize this yet' notice. There is no rule-level true/false positive distinction: every diagnostic is a real Compiler limitation rather than a defect in your code.

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.

Refactor the affected code into a shape the Compiler supports today (often hoisting an inner function, splitting a giant component, or removing a dynamic pattern). If a workaround is not feasible, add a 'use no memo' directive at the top of the file so the Compiler skips it, and check the React Compiler issue tracker for an open ticket covering your pattern. See https://react.dev/reference/eslint-plugin-react-hooks

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-hooks-js/todo diagnostic in the current repository.

Required change:

  • Refactor the affected code into a shape the Compiler supports today (often hoisting an inner function, splitting a giant component, or removing a dynamic pattern). If a workaround is not feasible, add a 'use no memo' directive at the top of the file so the Compiler skips it, and check the React Compiler issue tracker for an open ticket covering your pattern. See https://react.dev/reference/eslint-plugin-react-hooks

Validation before editing:

Hint-severity diagnostic the Compiler emits when it bails on a feature it should support but has not yet implemented: not a code mistake, more of a 'Compiler cannot optimize this yet' notice. There is no rule-level true/false positive distinction: every diagnostic is a real Compiler limitation rather than a defect in your code.

Constraints:

  • Confirm every occurrence independently.
  • Make the smallest change that addresses the root cause.
  • Preserve unrelated behavior, interfaces, content, and semantics.
  • Reuse existing project conventions and components.
  • Do not suppress the rule merely to clear the report.

Assessment:

  • Record detector evidence, applicability, missing evidence, and one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.

Verification:

  • Run focused tests and every repository-mandated check.
  • Run React Doctor and confirm the diagnostic no longer appears from changed code.
  • Run an unfiltered scan of the affected scope before claiming no cross-category regression.
  • Report checks that were not run instead of claiming they passed.