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.