Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add an option to report why did the owner render
See original GitHub issueI use WDYR extensively, and I find myself doing the following quite often:
— See a re-render warning about MyComponent with “This could have been avoided <…> by preventing its father from re-rendering”
— Find this particular usage of MyComponent, and identify its owner (“father”): OwnerComponent
— Re-run WDYR, this time with {include: [/^MyComponent$/, /^OwnerComponent$/], logOnDifferentValues: true}, to find out which particular (maybe useful) re-render of OwnerComponent caused the useless re-render of MyComponent
It would be nice If I could see the reason of owner’s re-render right away. If such a feature is welcome, I’ll be happy to send a PR
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
sure let’s give it a try. sounds great
implemented!