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 #108

Open
falcon027 opened this issue May 7, 2020 · 2 comments
Open

componentWillReceiveProps #108

falcon027 opened this issue May 7, 2020 · 2 comments

Comments

@falcon027
Copy link

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

  • node_modules/expo/build/logs/LogSerialization.js:166:14 in _captureConsoleStackTrace
  • node_modules/expo/build/logs/LogSerialization.js:41:24 in serializeLogDataAsync
  • ... 9 more stack frames from framework internals
@falcon027
Copy link
Author

#109

@alessiocancian
Copy link

I released the fix to npm, read #131

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

2 participants