Bug 2041475 - React components should have a (mostly) unique name in react dev tools to simplify code analyses
Summary: React components should have a (mostly) unique name in react dev tools to sim...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Christoph Jerolimov
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-17 12:51 UTC by Christoph Jerolimov
Modified: 2022-03-10 16:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:40:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10858 0 None open Bug 2041475: Add function names to components which are wrapped in memo to get their name in the react dev tools 2022-01-17 12:54:17 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:40:19 UTC

Description Christoph Jerolimov 2022-01-17 12:51:07 UTC
Description of problem:
As a console developer I would like to see unique component names in the react dev tools to simplify code analyses.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install react dev tools in your browser and open them
2. Open dev console

Actual results:
Many anonymous/unknown components are shown

Expected results:
Less anonymous/unknown components are shown

Additional info:

Comment 3 Vikram Raj 2022-01-24 13:50:53 UTC
Verified. Now able to see the component name in devtool.

Comment 6 errata-xmlrpc 2022-03-10 16:40:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.