`react-doctor/r3f-no-null-loader-input`

Nullish R3F loader input

Category: Bugs
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: react, r3f
Tags: r3f, webgl
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-null-loader-input. 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

const model = useGLTF(url ?? null);
return <primitive object={model.scene} />;

Corrected pattern

const Model = ({ url }) => {
  const model = useGLTF(url);
  return <primitive object={model.scene} />;
};
return url ? <Model url={url} /> : null;

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-null-loader-input diagnostic in the current repository. Required change: - Conditionally render a child component that calls the loader hook only after it has a real asset URL.

Reference transformation:Before:

const model = useGLTF(url ?? null);
return <primitive object={model.scene} />;

After:

const Model = ({ url }) => {
  const model = useGLTF(url);
  return <primitive object={model.scene} />;
};
return url ? <Model url={url} /> : null;

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-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-require-frame-delta: Frame-rate-dependent animation
react-doctor/r3f-require-global-effect-cleanup: Unreleased global R3F render-loop effect
react-doctor/r3f-require-instanced-buffer-update: Instanced mesh buffer is not marked for upload

react-doctor/r3f-no-null-loader-input