Bug: The ESLint react-hooks/refs rule marks the entire object with the ref property as a ref object

[4eb0da]

eslint-plugin-react-hooks version: 7.0.1

Steps To Reproduce

const Test = props => {
    return (
        <div>
            <button ref={props.buttonRef}>
                {props.text}
            </button>
        </div>
    );
};

The current behavior

The rule warns in both props props.buttonRef and props.text

The expected behavior

Errors in the rules are not expected.

This can be easily fixed as follows:

const Test = props => {
    const { buttonRef } = props;

    return (
        <div>
            <button ref={buttonRef}>
                {props.text}
            </button>
        </div>
    );
};

Simple logic tells me that the destructuring of variables should be equivalent to the direct use of prop in terms of rule errors.
The rule incorrectly marks props how to ref instead of `props.buttonRef'?

[Crhist0]

I'm getting the same error

[juoboinshurima543-sys]

That’s clear thanks

…

On Tue, Jan 20, 2026 at 7:50 PM 4eb0da ***@***.***> wrote: *4eb0da* created an issue (facebook/react#35575) <#35575> eslint-plugin-react-hooks version: 7.0.1 Steps To Reproduce const Test = props => { return ( <div> <button ref={props.buttonRef}> {props.text} </button> </div> );}; The current behavior The rule warns in both props props.buttonRef and props.text The expected behavior Errors in the rules are not expected. This can be easily fixed as follows: const Test = props => { const { buttonRef } = props; return ( <div> <button ref={buttonRef}> {props.text} </button> </div> );}; Simple logic tells me that the destructuring of variables should be equivalent to the direct use of prop in terms of rule errors. The rule incorrectly marks props how to ref instead of `props.buttonRef'? — Reply to this email directly, view it on GitHub <#35575>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B4CX3EQDSFI7E65JHILX2TL4H2BHNAVCNFSM6AAAAACSKCUX7CVHI2DSMVQWIX3LMV43ASLTON2WKOZTHAZTKMJWGE2TAMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>