-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Enable ESLint react/no-deprecated #24471
Conversation
@takayamaki maybe you have an idea of how these should be correctly updated to non-deprecated calls |
In fact, I am not used to writing class-based components. Other hand, hooks components are modern and simple. I seem better to rewrite these components with hooks. |
fb3b367
to
c10e302
Compare
afaik there are places where we do really rely on the old lifecycle methods and doing otherwise would require a very significant amount of work; that should only be a small portion of the code, though |
Yes, these deprecated life-cycle functions are just the tip of that iceberg. |
c10e302
to
649743d
Compare
This pull request has merge conflicts that must be resolved before it can be merged. |
Ran `npx react-codemod rename-unsafe-lifecycles`
649743d
to
09e553c
Compare
This pull request has resolved merge conflicts and is ready for review. |
@renchap I ran the same autoconversion of the events from your React 18 PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good with me 👍
Opening as a draft to flag the current issues with https://legacy.reactjs.org/docs/react-component.html#unsafe_componentwillreceiveprops
These would be things needed to upgrade beyond React 16