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

Warning: ComponentWillReceiveProps has been renamed #33

Open
shtbik opened this issue Dec 2, 2019 · 2 comments
Open

Warning: ComponentWillReceiveProps has been renamed #33

shtbik opened this issue Dec 2, 2019 · 2 comments

Comments

@shtbik
Copy link

shtbik commented Dec 2, 2019

react: 16.9.13

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
@shtbik shtbik closed this as completed Dec 2, 2019
@shtbik shtbik reopened this Dec 2, 2019
@KevinSeghetti
Copy link

KevinSeghetti commented Jan 29, 2020

Any plans to address this? I am actively using this library, it works great, but have recently updated to react 16, so am getting these warnings.
Looks like there is a pull request from dan-lee which patches this. (I tried having npm fetch from that branch, but doesn't seem to have a prepare script, so doesn't work directly).

I have worked around this problem by making a release of dan-lee's version onto npmjs called "kevinseghetti-react-cursor-position": "^3.0.3",

@redheet
Copy link

redheet commented Oct 9, 2022

Any plans to address this? I am actively using this library, it works great, but have recently updated to react 16, so am getting these warnings.

Looks like there is a pull request from dan-lee which patches this. (I tried having npm fetch from that branch, but doesn't seem to have a prepare script, so doesn't work directly).
I have worked around this problem by making a release of dan-lee's version onto npmjs called "kevinseghetti-react-cursor-position": "^3.0.3",

thank you work using kevinseghetti-react-cursor-position

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

3 participants