`react-doctor/r3f-no-imperative-attach-of-managed-ref`

Imperative attachment of an R3F-managed ref

Category: Bugs
Severity: error
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: react, r3f
Tags: r3f, webgl, react-jsx-only
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/r3f-no-imperative-attach-of-managed-ref. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

useEffect(() => {
  scene.add(mesh.current);
}, [scene]);
return <mesh ref={mesh} />;

Corrected pattern

return <mesh ref={mesh} />;

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/r3f-no-imperative-attach-of-managed-ref diagnostic in the current repository. Required change: - Let R3F attach objects referenced by JSX. Do not add or attach the same ref.current imperatively.

Reference transformation:Before:

useEffect(() => {
  scene.add(mesh.current);
}, [scene]);
return <mesh ref={mesh} />;

After:

return <mesh ref={mesh} />;

Constraints: - Confirm the reported code matches the Before pattern. - 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. - Confirm this rule is enabled for the project: react, r3f. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Bugs rules from the rules reference:

react-doctor/r3f-no-mutate-loader-cache: Mutation of a cached R3F loader asset
react-doctor/r3f-no-mutating-pointer-event-data: Mutation of shared R3F pointer-event data
react-doctor/r3f-no-null-loader-input: Nullish R3F loader input
react-doctor/r3f-no-object-pointer-capture: Pointer capture called on an R3F scene object
react-doctor/r3f-no-use-frame-dependency-array: Dependency array passed to useFrame

react-doctor/r3f-no-imperative-attach-of-managed-ref