fix(no-forward-ref): loose fix

[hyoban]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• I have added a convincing reason for adding this feature, if necessary

Other information

This can reduce the amount of code users need to modify after auto-fixing lint

[vercel]

@hyoban is attempting to deploy a commit to the Rel1cx's projects Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
eslint-react	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 23, 2025 3:46pm

[Rel1cx]

The current fix follows the remove-forward-ref in the official React codemod https://github.com/reactjs/react-codemod/blob/master/transforms/remove-forward-ref.ts.

Can you list some real-world examples where the types used in the current fix are not compatible, while the ones in this PR are?

[hyoban]

We may be able to refer to React.DetailedHTMLProps, defined as ref?: Ref<T> | undefined, and Ref is RefCallback<T> | RefObject<T | null> | null.

And we may be able to use React.Ref directly. Did I miss something?

If the ref of a component is required, don't we need to pass the ref in every place?

[Rel1cx]

If the ref of a component is required, don't we need to pass the ref in every place?

The ref prop is passed by React, not by user. I tend to keep the existing fixes for a while longer to see if @types/react gets updated.