Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

componentWillReceiveProps has been renamed, and is not recommended for use. #3770

Closed
vibhorme opened this issue Sep 21, 2019 · 4 comments
Closed

Comments

@vibhorme
Copy link

While using the react-select v2 Async Select component there is a warning being rendered in the devtools regarding the use of componentWillRecieveProps, which has been updated and renamed in the new Updates in ReactJs.

The warning is

Warning: componentWillReceiveProps has been renamed, and is not recommended for use.

  • Move data fetching code or side effects to componentDidUpdate.
  • If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
  • Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Can we update the files of the async and select folder present in the node_modules because it needs to be updated as per the new code structure in ReactJs

@mpopv
Copy link

mpopv commented Sep 23, 2019

Duplicate of #3720

@ranneyd
Copy link

ranneyd commented Sep 25, 2019

#3720 (comment)

You can use this while this lib gets sorted out

@ranneyd
Copy link

ranneyd commented Oct 2, 2019

Latest version of lib is fixed fyi

@emmatown
Copy link
Collaborator

emmatown commented Oct 3, 2019

Thanks for the issue, closing since this is now fixed!

@emmatown emmatown closed this as completed Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants