welldone-software/why-did-you-render

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

Open

Aperta il 15 mar 2023

Vedi su GitHub
 (2 commenti) (1 reazione) (0 assegnatari)JavaScript (10.560 star) (188 fork)batch import
enhancementgood first issuehelp wanted

Descrizione

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?

Guida contributor

Tech stack
javascriptreactreact native
Dominio
frontendmobile
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Familiarity with React component renderingUnderstanding of the why did you render library
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
60
Direzione di ricerca
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=...]'.