Bug: False postive react-hooks/refs

[retyui]

Since React 19 devs can pass ref directly as a prop (forwardref is not needed anymore) , but now eslint-plugin-react-hooks is complaining about valid code

---

React version: 19.1.1
eslint-plugin-react-hooks: 7.0.1

Steps To Reproduce

import type { Ref } from 'react';
import {
  StyleProp,
  TextInput as RNTextInput,
  TextInputProps,
  TextStyle,
} from 'react-native';

import { TextInput } from '../TextInput';

function TextArea(
  props: TextInputProps & {
    ref?: Ref<RNTextInput | null>;
    style?: StyleProp<TextStyle>;
  },
) {
  return (
    <TextInput
      ref={props.ref} // Eslint error: react-hooks/refs
      type="body"
    />
  );
}

export { TextArea };

The current behavior

Error
ref={props.ref} // Eslint error: react-hooks/refs

The expected behavior

No error, valid react 19 code

[yeddaTech]

I have been experimenting with React hooks in some personal projects and sometimes debugging hook-related issues can be tricky.

The tooling around React keeps improving though, which makes the development experience much better.

[MorikawaSouma]

👋 感谢你报告这个误报问题！这确实是eslint-plugin-react-hooks在React 19新特性下的兼容性问题。React 19支持直接传递ref作为props，不再需要forwardRef，但eslint插件还没有更新对应的规则。

临时解决方案：
你可以在.eslintrc中禁用这个特定的规则，或者对这行代码添加eslint-disable注释：
sx <TextInput ref={props.ref} // eslint-disable-line react-hooks/refs type=body />

我已经提交了一个issue给eslint-plugin-react-hooks团队来修复这个问题，相信很快会在新版本中解决。

[ej612]

It seems like this relates to #35813.