react-redux 7 uses useMemo, all Connected components complaining
See original GitHub issueGreat job on the new release! I just updated react-redux to 7.0.1 and WDYR is complaining about every single one. How should we handle this?
Connect(Header)
whyDidYouRender.min.js:8 {Connect(Header): ƒ} "Re-rendered because of hook changes:"
whyDidYouRender.min.js:8 hook useMemo
whyDidYouRender.min.js:8 different React elements with the same displayName. (more info at http://bit.ly/wdyr3)
whyDidYouRender.min.js:8 {"prev ": {…}} "!==" {"next ": {…}}
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
How to use React.memo with react-redux connect?
memo is to check if all the new props received by the component are the same as the last props. If any HOC...
Read more >Understanding common frustrations with React Hooks
React Hooks can be frustrating despite their popularity and widespread use. Learn about some of the drawbacks to using React Hooks.
Read more >React.useMemo and when you should use it - everyday.codes
memo should only be applied to pure components. Another issue has to do with Redux/Context and hooks. Before hooks, the Redux selectors passed ......
Read more >The Hate around Redux and co? : r/reactjs - Reddit
I recently built a small ToDoList app where the AddItemForm was a separate component that was packed in another component and I found...
Read more >Why React Re-Renders | Hacker News
He says "useRef offering a connection to DOM elements is just sugar", but that's not ... Probably better to use useMemo with []...
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 FreeTop 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
Top GitHub Comments
solved in react-redux@7.0.2 (by me 😛)
I believe we discovered a small performance issue with react-redux 😃 I fixed it there.