welldone-software/why-did-you-render

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

Open

#269 opened on Mar 15, 2023

View on GitHub
 (2 comments) (1 reaction) (0 assignees)JavaScript (10,560 stars) (188 forks)batch import
enhancementgood first issuehelp wanted

Description

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?

Contributor guide

Tech stack
javascriptreactreact native
Domain
frontendmobile
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with React component renderingUnderstanding of the why did you render library
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
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=...]'.