jsx-eslint/eslint-plugin-react

prop-types: children and React.VFC

Open

#2,913 创建于 2021年2月1日

在 GitHub 查看
 (14 评论) (3 反应) (0 负责人)JavaScript (8,630 star) (2,797 fork)batch import
help wantedtypescript

描述

There is now a way to properly communicate the absence of the children prop at the TypeScript level: React.VFC (vs React.FC). React.VFC aka React.VoidFunctionComponent does not allow children prop, the prop-types rule should derive the presence/absence of children from the underlying TypeScript types (when used with TypeScript).

Related: #7.

贡献者指南

技术栈
javascripttypescriptreact
领域
frontend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Understanding of React TypeScript typesFamiliarity with eslint plugin react internals
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
The issue requests extending the prop types rule to support React.VFC, which does not allow children prop. Start by reviewing the existing prop types rule implementation (likely in lib/rules/prop types.js) and the related issue #7 for context. Look for how the plugin currently infers type definitions from TypeScript. Consider adding detection of React.VFC (or React.VoidFunctionComponent) and updating the logic to recognize that these types imply no children prop. The solution involves parsing TypeScript types within the AST and checking the component's type reference.