[Bug]: `react/no-object-type-as-default-prop` is disabled when using a `ref` prop about eslint-plugin-react

[ljharb]

That’d be great, thanks!

[ljharb]

That's because forwardRef's callback is not a component. Function components take context as a second argument, not ref.

[JulienR1]

Actually, the issue does not come from the ref directly, it comes from having a second argument. If I use forwardRef as described in React's docs, I still don't get an error from eslint.

From what I can see, this behavior is caused by this line in the rule's implementation: having more than one argument in the function will not execute the rule.

Second test:

const ErrorIsShown = ({ foo = {} }) => null;
const ErrorIsAbsent = forwardRef(function({ foo = {} }, ref) {
    return null
});

[ljharb]

I see what you mean. Given that it's fine to have , context in a component, the rule should be triggered regardless of there being more than one param.

[JulienR1]

That is exactly it.
Do you want me to set up a PR fixing this?