No corresponding propTypes declaration when export type with typescript.

Description

// Will get error: defaultProp "data" has no corresponding propTypes declaration
// from react/default-props-match-prop-types
export type TableProps = {
  data?: any;
};

const defaultProps = {
  data: null,
};

const Table: FC<TableProps> = ({ data }) => null;

// working well
type TableProps = {
  data?: any;
};

const defaultProps = {
  data: null,
};

const Table: FC<TableProps> = ({ data }) => null;

Contributor guide

Tech stack

javascripttypescriptreactnodejs

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.

stale

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

clear

Prerequisites

Basic TypeScriptReact propTypes

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

50

Research direction

Investigate the ESLint rule 'react/default props match prop types' in the eslint plugin react repository. The issue occurs when a type is exported with the `export` keyword, causing a false positive. The fix likely involves adjusting the rule's logic to handle exported type aliases. Start by examining the rule implementation in 'lib/rules/default props match prop types.js' and any related utility functions. Consider the difference between `export type` and `type` declarations in TypeScript syntax trees.