react-doctor/forbid-dom-props

Configure forbidden DOM props via the `forbidDomProps.forbid` setting to keep disallowed attributes off DOM nodes.

Validation prompt

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

Fires only when a prop is configured in the forbidDomProps.forbid setting AND that prop name appears as a JSX attribute on a lowercase DOM tag (e.g. <div id> when id is forbidden); a per-prop disallowedFor list narrows it to specific tags (e.g. accept only on <form>). PascalCase components (<Foo>, <this.Foo>), namespaced tags (<fbt:param>), and props delivered only via spread (<div {...props} />) are never flagged.

Suppress when: a forbidden prop that is intentionally required on one element: confirm the team's convention actually forbids it there rather than suppressing blindly, since this rule is purely a project-defined policy with no inherent correctness signal.

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.

Remove or rename the forbidden attribute to the project-sanctioned alternative the policy intends: for example swap a banned className for the team's preferred prop, or drop accept from <form> and place it on the <input> instead (<input type="file" accept="video/*" />). If the prop genuinely belongs there, either narrow the rule's disallowedFor list to exclude that tag or add a justified disable comment on that line. See https://oxc.rs/docs/guide/usage/linter/rules/react/forbid-dom-props

Repository-wide copy prompt

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