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

Deprecation warning with React 16.13: "Warning: componentWillReceiveProps has been renamed" #192

Closed
gustaff-weldon opened this issue Jul 3, 2020 · 5 comments · May be fixed by #196
Closed

Deprecation warning with React 16.13: "Warning: componentWillReceiveProps has been renamed" #192

gustaff-weldon opened this issue Jul 3, 2020 · 5 comments · May be fixed by #196

Comments

@gustaff-weldon
Copy link

Using latest React (16.13.1 as of writing) gives deprecation warning with Dropdown component:

     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: Dropdown
@hamidone
Copy link

I have the same problem.

How can I solve this problem?

@bendikiv
Copy link

Same here.

@wtesler
Copy link

wtesler commented Aug 15, 2020

Same

@HarryHenryGebel HarryHenryGebel mentioned this issue Aug 18, 2020
Open
@HarryHenryGebel
Copy link

HarryHenryGebel commented Aug 18, 2020 •
edited
Loading

The component functions as normal without the deprecated method, I removed it and put in a pull request.

@fraserxu
Copy link
Owner

Sorry for the delay, change has been deployed as in #170

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.

Fix issue #192 HarryHenryGebel/react-dropdown
6 participants
@gustaff-weldon @fraserxu @HarryHenryGebel @wtesler @bendikiv @hamidone