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.

Sign up for GitHub

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

Jump to bottom

Remove depracated in react 16.9 componentWillReceiveProps #171

Closed
Akiyamka opened this issue Aug 23, 2019 · 0 comments · May be fixed by #186
Closed

Remove depracated in react 16.9 componentWillReceiveProps #171

Akiyamka opened this issue Aug 23, 2019 · 0 comments · May be fixed by #186

Comments

@Akiyamka
Copy link
Contributor

After upgrade to react 16.9 new warning trown:

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.

This strings modules need to fix:
https://github.com/developit/unistore/search?q=componentWillReceiveProps&unscoped_q=componentWillReceiveProps
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

WIP fix #171 Convert react integration to use hooks lkmill/unistore
1 participant
@Akiyamka