-
-
Notifications
You must be signed in to change notification settings - Fork 2.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
Add no-unsafe
rule
#1830
Labels
Comments
Merged
The rule has been merged. |
This was referenced Sep 22, 2018
Closed
This was referenced Oct 27, 2018
This was referenced Nov 4, 2018
This was referenced Nov 23, 2018
1 task
1 task
1 task
This was referenced Dec 21, 2018
This was referenced Jan 2, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Certain legacy lifecycle methods are unsafe for use in async React applications and cause warnings in strict mode:
UNSAFE_componentWillMount
UNSAFE_componentWillReceiveProps
UNSAFE_componentWillUpdate
.These also happen to be the lifecycles that cause the most confusion within the React community. At the same time there're no deprecation warnings regarding using
UNSAFE_
methods and it will still be possible to use them in React 17.The rule prevents usage of of
UNSAFE_
lifecycle methods. See discussion details #1750 (comment).The text was updated successfully, but these errors were encountered: