welldone-software/why-did-you-render

Is it possible to print testID along side Component name on wdyr logs?

Open

#269 建立於 2023年3月15日

在 GitHub 查看
 (2 留言) (1 反應) (0 負責人)JavaScript (10,560 star) (188 fork)batch import
enhancementgood first issuehelp wanted

描述

I did not saw a discussion tab so I will post this here. It is not a bug, it is more of a question or suggestion.

I have been using wdyr for the first time in the last couple of days and I believe could be helpful if I can identify the components faster in the logs. Sometimes I see that a Pressable rendered again but my screen has multiple Pressables in multiple places. Reading the logs further help understand what is the exactly component but I believe that using an easier method could speed things up.

What do you think?

貢獻者指南

技術棧
javascriptreactreact native
領域
frontendmobile
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Familiarity with React component renderingUnderstanding of the why did you render library
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Review the current logging format in the why did you render source code (likely in src/monkeyPatch.js or similar). Understand how component names are currently extracted. Investigate how to access the testID prop from React components, possibly via the fiber or component instance. Check if there are existing tests or examples that show the current output. Consider the user's request for a comma separated or appended format, e.g., 'ComponentName [testID=...]'.