Deprecated UNSAFE_componentWillReceiveProps
See original GitHub issueHi, thanks for a very helpful library!
I’ve turned “React Strict mode” today and was greeted with following warning: “Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.”
This hook is used in the wrapper function of your library and judging by your comment - If someone knows a better way to replace this with sync hook that can dispatch before render let me know
- you probably already know that this method will be deprecated.
Just wanted to ask what are your plans with this then? Thanks again, P!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:14 (8 by maintainers)
Top Results From Across the Web
React.Component
UNSAFE_componentWillReceiveProps (). Unmounting. This method is called when a component is being removed from the DOM: componentWillUnmount() ...
Read more >React17, or how to get rid of “componentWillReceiveProps”?
As you may already know, with the release of React 16.3, some of legacy lifecycles were deprecated. One of the biggest lessons we've...
Read more >ReactJS UNSAFE_componentWillReceiveProps() Method
The componentWillReceiveProps() method has been deprecated in the latest releases of React as per this issue.
Read more >Warning: componentWillReceiveProps has been ... - GitHub
With the release of React 16.3, some new lifecycle methods have been introduced, and release of React 17 will deprecate some lifecycle method....
Read more >componentWillMount is deprecated and will be removed in the ...
I use the react native latest version of 0.54.0 and Whenever run the apps on iOS there is found warning about deprecate the...
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
Nothing. It is working. It is surely annoying but it does not affect anything. The fix is on the way.
Released 7.0.4