No corresponding propTypes declaration when export type with typescript.

描述

// 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;

貢獻者指南

技術棧

javascripttypescriptreactnodejs

領域

frontendtooling

議題類型

bug

難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。

3

預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。

1-3 hours

活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。

stale

清晰度議題是否清楚說明預期改動、驗收標準和下一步。

clear

前置要求

Basic TypeScriptReact propTypes

新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。

50

研究方向

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.