Do you want to request a feature or report a bug?
bug
What is the current behavior?
I can't rely on data from context API by using (useContext hook) to prevent unnecessary rerenders with React.memo
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:
React.memo(() => {
const [globalState] = useContext(SomeContext);
render ...
}, (prevProps, nextProps) => {
// How to rely on context in here?
// I need to rerender component only if globalState contains nextProps.value
});
What is the expected behavior?
I should have somehow access to the context in React.memo second argument callback to prevent rendering
Or I should have the possibility to return an old instance of the react component in the function body.
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
16.8.4
Telokis, julienbrunuk, MaxGorshkov, huximing, paramsinghvc and 121 moreTanzhenglongInnocentScott, LofizDev, moro4, duylam0043 and merabteneidadabarbast and rogeralbinoidadabarbast, hrdyjan1, DaniAkash, pouyajabbarisani, tigrankeshishyan and 2 morepouyajabbarisani, idontknowjs, emmacv, JoseDone16 and merabteneixgqfrms and duylam0043
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4