# `react-doctor/r3f-no-state-in-pointer-move`

React state update inside an R3F pointer-move handler

- **Category:** Performance
- **Severity:** warn
- **Source:** oxlint-plugin-react-doctor
- **Framework:** global
- **Enabled when:** react, r3f

## Validate the diagnostic

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

Confirm the reported code matches `react-doctor/r3f-no-state-in-pointer-move`. 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

```tsx
import { useState } from "react";
import "@react-three/fiber";
const Draggable = () => {
  const [position, setPosition] = useState(() => new Vector3());
  return <mesh
    position={position}
    onPointerMove={(event) => setPosition(event.point.clone())}
  />;
};
```

### Corrected pattern

```tsx
import { useRef, useState } from "react";
import "@react-three/fiber";
const Draggable = () => {
  const [position, setPosition] = useState(() => new Vector3());
  const mesh = useRef(null);
  return <mesh
    ref={mesh}
    position={position}
    onPointerMove={(event) => mesh.current.position.copy(event.point)}
    onPointerUp={(event) => setPosition(event.point.clone())}
  />;
};
```

## 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.

````text
Fix every confirmed `react-doctor/r3f-no-state-in-pointer-move` diagnostic in the current repository.

Required change:
- Keep pointer-move previews in Three.js refs or transient state and publish one semantic React update when the interaction commits.

Reference transformation:

Before:
```tsx
import { useState } from "react";
import "@react-three/fiber";
const Draggable = () => {
  const [position, setPosition] = useState(() => new Vector3());
  return <mesh
    position={position}
    onPointerMove={(event) => setPosition(event.point.clone())}
  />;
};
```

After:
```tsx
import { useRef, useState } from "react";
import "@react-three/fiber";
const Draggable = () => {
  const [position, setPosition] = useState(() => new Vector3());
  const mesh = useRef(null);
  return <mesh
    ref={mesh}
    position={position}
    onPointerMove={(event) => mesh.current.position.copy(event.point)}
    onPointerUp={(event) => setPosition(event.point.clone())}
  />;
};
```

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.
- Preserve resource ownership and cleanup. Do not move work into a hotter render or frame path.
- 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.
````