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 Warning #27

Closed
allanalves23 opened this issue Jan 28, 2020 · 2 comments · Fixed by #28
Closed

Comments

@allanalves23
Copy link

allanalves23 commented Jan 28, 2020

Its not a bug, but a warning.
I received react warning from Password Field with componentWillReceiveProps Method.
This component will be updated?
See below the warning:

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles 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: PasswordField

how can i solve this?

@leMaik
Copy link
Member

leMaik commented Mar 5, 2020

Let's keep this open until it is solved. Since you alreaedy looked up how to solve this (we need the second option here), you could submit a PR to remove the warning. 😉

Edit: Oh wow, I didn't see that this has been open for over a month. I'll fix it asap.

@leMaik leMaik reopened this Mar 5, 2020
@allanalves23
Copy link
Author

Let's keep this open until it is solved. Since you alreaedy looked up how to solve this (we need the second option here), you could submit a PR to remove the warning.

Edit: Oh wow, I didn't see that this has been open for over a month. I'll fix it asap.

Don't worry, I can solve this.
I submit a PR coming soon.

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

Successfully merging a pull request may close this issue.

2 participants