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

Console warnings with latest react version #550

Closed
1 task done
shafaq-kazmi opened this issue Oct 10, 2019 · 3 comments
Closed
1 task done

Console warnings with latest react version #550

shafaq-kazmi opened this issue Oct 10, 2019 · 3 comments

Comments

@shafaq-kazmi
Copy link

  • I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Everything is fine after updating to react latest version

Current Behavior

There is a warning in the console

react-dom.development.js:12487 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: ReactSwipableView

Steps to Reproduce (for bugs)

  1. Update react to the latest version

Context

Your Environment

Tech Version
react-swipeable-views 0.13.3
React 16.10.2
platform
etc
@shilangyu
Copy link

Duplicate of #534

@caleb-harrelson
Copy link
Collaborator

Workaround implemented in #616, release coming soon.

@Dar0n
Copy link

Dar0n commented Jul 20, 2022

This is not completed, the mentioned fix was never published in an official release.

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

4 participants