welldone-software/why-did-you-render

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

Open

#269 opened on 2023年3月15日

GitHub で見る
 (2 comments) (1 reaction) (0 assignees)JavaScript (10,560 stars) (188 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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=...]'.
Is it possible to print testID along side Component name on wdyr logs? · welldone-software/why-did-you-render#269 | Good First Issue