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

Deprecation warning for incoming React 17 #118

Open
sergentn opened this issue Sep 25, 2019 · 7 comments
Open

Deprecation warning for incoming React 17 #118

sergentn opened this issue Sep 25, 2019 · 7 comments

Comments

@sergentn
Copy link

Hi,
After updating React to 16.9.0, I am getting these warnings in Firefox:

Deprecation Warning

By the way, is this project still active ?
Thanks,

@burtek
Copy link

burtek commented Dec 12, 2019

By the way, is this project still active ?

Does not look like this :(

@DragonChen-TW
Copy link

DragonChen-TW commented Dec 15, 2019

It's inactivate, I think.
But I'm interested in maintain it
Contact me if anyone else already have some progress.

@AntonOellerer
Copy link

Do you know of any maintained fork?

@AntonOellerer
Copy link

AntonOellerer commented Feb 25, 2020

Fyi, I just moved to the normal html <input type="number">

@stahlmanDesign
Copy link

stahlmanDesign commented Aug 11, 2021

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://reactjs.org/link/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://reactjs.org/link/derived-state
  • Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 18.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: NumericInput

It would be very easy to fix this warning.

Simply Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps in line 410 of this file

@burtek
Copy link

burtek commented Sep 23, 2021

this project seems dead at this point...

@bflamand
Copy link

Anyone with a managed fork containing this fix? This issue will become even more problematic when upgrading to the newly released React 18...

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

6 participants