Add no-unsafe rule
#1830
Labels
Comments
Merged
|
The rule has been merged. |
calebeby
pushed a commit
to Pigmice2733/scouting-frontend
that referenced
this issue
Jun 30, 2018
This Pull Request updates dependency [eslint-plugin-react](https://github.com/yannickcr/eslint-plugin-react) from `v7.9.1` to `v7.10.0` <details> <summary>Release Notes</summary> ### [`v7.10.0`](https://github.com/yannickcr/eslint-plugin-react/blob/master/CHANGELOG.md#​7100---2018-06-24) [Compare Source](jsx-eslint/eslint-plugin-react@v7.9.1...v7.10.0) ##### Added * Allow eslint ^5 ([#​1843][] @​papandreou, @​ljharb) * [`no-unsafe`][] rule ([#​1831][], [#​1830][] @​sergei-startsev) * [`no-will-update-set-state`][]: Account for `UNSAFE_` methods ([#​1845][], [#​1844][] @​alexzherdev) ##### Fixed * [`no-typos`][]: Fix static propTypes handling ([#​1827][], [#​1677][] @​alexzherdev) * [`destructuring-assignment`][]: Allow LHS ([#​1825][], [#​1728][] @​alexzherdev) * [`no-unused-prop-types`][]: Fix crash when encountering mixed union and intersection flow types ([#​1806][] @​yannickcr) ##### Changed * Typo fixes in [`jsx-no-target-blank`][] ([#​1805][] @​ferhatelmas)) [#​1845]: `jsx-eslint/eslint-plugin-react#1845 [#​1844]: `jsx-eslint/eslint-plugin-react#1844 [#​1843]: `jsx-eslint/eslint-plugin-react#1843 [#​1831]: `jsx-eslint/eslint-plugin-react#1831 [#​1830]: `jsx-eslint/eslint-plugin-react#1830 [#​1827]: `jsx-eslint/eslint-plugin-react#1827 [#​1825]: `jsx-eslint/eslint-plugin-react#1825 [#​1806]: `jsx-eslint/eslint-plugin-react#1806 [#​1805]: `jsx-eslint/eslint-plugin-react#1805 [#​1728]: `jsx-eslint/eslint-plugin-react#1728 [#​1677]: `jsx-eslint/eslint-plugin-react#1677 --- </details> --- This PR has been generated by [Renovate Bot](https://renovatebot.com).
This was referenced Sep 22, 2018
Closed
This was referenced Sep 23, 2018
Open
Open
Open
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_componentWillMountUNSAFE_componentWillReceivePropsUNSAFE_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: