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 warning #16

Closed
Penguinatormike opened this issue Sep 23, 2019 · 2 comments
Closed

componentWillReceiveProps warning #16

Penguinatormike opened this issue Sep 23, 2019 · 2 comments

Comments

@Penguinatormike
Copy link

update react-select from 3.0.4 => 3.0.5 in package.json

@Penguinatormike
Copy link
Author

Updating should get rid of this message:

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

  • 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.

Please update the following components: AutosizeInput

@guiyep
Copy link
Owner

guiyep commented Sep 24, 2019

This is not an issue of this library. It is coming from react-select with react 16.9. Please follow this react-select issue that it is still open. JedWatson/react-select#3720

You are using peer deps so you can use any version you want but the one recommended so far are specified in the readme.

@guiyep guiyep closed this as completed Sep 24, 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

2 participants