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.
Bug in useMemo (?)
See original GitHub issueI noticed a problem with useEffect() - the second argument (changed props) which gets passed on through to useMemo(), is not respected: the effect is triggered every time anything updates; even if the component itself doesn’t update and another component on the page does.
As you can see in this example, the component should only update if count has changed - but the effect runs for all three components:
I narrowed it down to to useMemo(), where the last time triggers the change every time:
As you can see, it correctly detects that isChange is false - but still triggers the update, because isMounted is always undefined.
I will try to add a failing test for this problem.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 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
Looks good now, thanks!
https://codesandbox.io/s/fre-demo-uxuic