react-doctor/no-render-in-render

A render helper is reconciled normally; extract a component only when it needs an independent identity, state, or reusable boundary

Validation prompt

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

Fires on a JSX expression {callee(...)} or {obj.method(...)} where the callee name matches render followed by an uppercase letter. Calling a helper that returns JSX does not itself remount descendants: React reconciles the returned element types, keys, and positions as part of the parent's output. Treat this as an architecture review and confirm extraction would create a useful component boundary rather than only rename the same inline rendering logic.

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.

Keep a small single-use render helper inline when the call site remains clearer. Extract a module-scope component only when the subtree needs its own state, lifecycle, memoization boundary, DevTools identity, or meaningful reuse; pass closure values as props and preserve existing element keys and positions. Do not claim the helper was remounting children without runtime evidence. See https://react.dev/learn/preserving-and-resetting-state

Repository-wide copy prompt

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