componentWillReceiveProps
See original GitHub issueHi. I get a warning:
Warning: componentWillReceiveProps has been renamed, and is not recommended for use. Please update the following components: Pie, PieChart
and others, I suppose.
Do you plan to update package?
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
React.Component
This lifecycle was previously named componentWillReceiveProps . That name will continue to work until version 17. Use the rename-unsafe-lifecycles codemod ...
Read more >When to use componentWillReceiveProps lifecycle method?
componentWillReceiveProps () is invoked before a mounted component receives new props. If you need to update the state in response to prop ...
Read more >ReactJS – componentWillReceiveProps() Method
This method is used during the updating phase of the React lifecycle. This function is generally called if the props passed to the...
Read more >React17, or how to get rid of “componentWillReceiveProps”?
This event hook is basically componentWillReceiveProps , but worse. It happens just before render, but you can't use this.setState() .
Read more >Replacing 'componentWillReceiveProps' with ' ...
Replacing 'componentWillReceiveProps' with 'getDerivedStateFromProps'. With the release of React 16.3, some new lifecycle methods have been introduced, and ...
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
@xile611 @githubloverforever I can still see UNSAFE methods in 2.0.0-beta.6 I understand why the change to remove UNSAFE methods was reverted (https://github.com/recharts/recharts/pull/1905), but is there a plan to completely get rid of UNSAFE methods in 2.x ? https://github.com/recharts/recharts/issues/1910 does not mention this as part of the roadmap
Try Reacharts 2.0.0-beta.5