[Bug]: False positive for react/no-unused-prop-types and passthrough

Description

export type TestProp = {
    name: string;
};

const Component1: FC<TestProp> = ({ name }) => {
    return <div>{name}</div>;
};

const Component2: FC<{ Component: FC<TestProp>; props: TestProp }> = ({ Component, props }) => {
    return <Component name={props.name} />;
};

const Component3: FC<TestProp> = (props: TestProp) => {
    return <Component2 Component={Component1} props={props} />;
};

Contributor guide

Tech stack

typescriptreactjavascript

Domain

frontendtooling

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

knowledge of ESLint plugin developmentunderstanding of React prop types

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

45

Research direction

Investigate the rule file 'lib/rules/no unused prop types.js' in the eslint plugin react repository. Focus on how the rule tracks prop usage across components, particularly when props are passed through (e.g., Component2 receives a Component and its props, then passes the prop to Component1). The false positive occurs when Component3 is present, suggesting the rule's analysis of prop passthrough chains is incomplete. Review the rule's logic for handling indirect prop usage and consider how to extend it to detect that 'name' is used via the passthrough pattern.