DevTools: Memo(ForwardRef()) and "Rendered By" List
See original GitHub issueIf you have memo(forwardRef(X))
, then the inner component won’t have a “rendered by” list. This is because it technically doesn’t have an owner. It is artificial.
I think we should ideally set up _debugOwner
for these Fibers in DEV just so existing tooling can find them. Or special case them in DevTools.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Why is React.forwardRef preventing this HOC from rendering ...
1. Problem. It's like a bug in devtools when you put React.forwardRef inside React.memo . Therefore, to know whether these Cell s are...
Read more >Forwarding Refs - React
Ref forwarding is a technique for automatically passing a ref through a component to one of its children. This is typically not necessary...
Read more >Optimize slow React components with “React Profiler”
Which component to wrap with memo or which callback is responsible for component re-rendering regardless of nothing changing in it's data.
Read more >How to use React's forwardRef function | Felix Gerschau
Our task is to forward the ref that the Input component receives to the HTML input element. We do that by wrapping the...
Read more >React Function Components
Props are the React Function Component's parameters. Whereas the component can stay generic, we decide from the outside what it should render ( ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@hanq08 If you’re interested in working on this, we’d welcome a PR.
bump