-
Notifications
You must be signed in to change notification settings - Fork 586
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
Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps #695
Comments
Yeah, Please merge this pull request ASAP. |
I looked at pull request. These are the changes that are needed. And I don't need to add pull request. Thanks for the quick response. I will wait for the package update |
I see the thread has merge in master. And when will the changes appear in the package? |
Note: This breaks react <16.3 support. |
+1 also waiting on updated package. |
+1 |
2 similar comments
+1 |
+1 |
from pull request, 17 days ago:
|
Fixed in #681 |
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: Autosuggest, Autowhatever.
Could you please update the component according to this message in console.log.
The text was updated successfully, but these errors were encountered: