Update componentWillReceiveProps

[lhtdesignde]

This lifecycle function is deprecated. Would be great if you could add UNSAFE prefix or generally refactor it to componentDidUpdate.

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: EnlargedImage

Thanks!

[ceisele-r]

Actually I think this will break completely in react 17 since those methods can then only be called with the unsafe_ name.

[hiahmedhameed]

Hello @ethanselzer,
Thank you for the nice library.

Do we expect any update regarding this warning soon ?

[spasticninja]

Version of react-image-magnify: 2.7.4

  console.warn
    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: ReactCursorPosition

[a-tonchev]

Issue still here, probably we need to make a fork