jsx-eslint/eslint-plugin-react

The react/display-name rule assumes displayNames are set that are not

Open

#2,150 创建于 2019年2月2日

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

描述

From what I can tell, @babel/plugin-transform-react-display-name only adds display names for components created with React.createClass or createReactClass, yet the react/display-name rule assumes the transpiler sets a displayName for components that extend React.Component and functional components.

If the transpiler referenced in the docs is referring to some other babel plugin, the docs should be updated to link to that plugin.

贡献者指南

技术栈
javascriptreact
领域
frontendtooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
basic React knowledgeunderstanding of ESLint pluginsfamiliarity with Babel transpilation
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
Investigate the behavior of @babel/plugin transform react display name to confirm whether it only adds display names for components created with React.createClass or createReactClass. Check the eslint plugin react documentation and source code for the react/display name rule to see where the assumption is made. Consider updating the documentation to clarify the transpiler reference or adjusting the rule to not assume display names are set by the transpiler.