azazdeaz / azazdeaz/react-gsap-enhancer
React v16.9.0 warns for using deprecated componentWillUpdate
- Dominant language
- JavaScript
- Stars
- 730
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
> Warning: componentWillUpdate 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.
> * Rename componentWillUpdate to UNSAFE_componentWillUpdate 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.
See https://scotch.io/bar-talk/whats-new-in-react-169#toc-renaming-unsafe-lifecycle-methods
What's the best approach to update react-gsap-enhancer to work with the upcoming React 17, and no longer throw this warning?
Contributor guide
Research direction
No files or tests are named. Start by locating componentWillUpdate in react-gsap-enhancer and reproduce the warning with React 16.9. Compare the available lifecycle-renaming guidance, then verify that the chosen update removes the warning and remains compatible with React 17.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100