-
Notifications
You must be signed in to change notification settings - Fork 14
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
An in-range update of eslint-plugin-react is breaking the build 🚨 #249
Comments
After pinning to 7.11.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes Release Notes for v7.12.1Fixed
Changed
CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v7.12.2Fixed
CommitsThe new version differs by 5 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v7.12.3Fixed
Changed
CommitsThe new version differs by 14 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v7.12.4Fixed
ChangedCommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 98 commits.
There are 98 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v7.14.0Added
Fixed
Changed
CommitsThe new version differs by 166 commits.
There are 166 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 169 commits.
There are 169 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 171 commits.
There are 171 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v7.14.3Fixed
ChangedCommitsThe new version differs by 185 commits.
There are 185 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 215 commits.
There are 215 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 219 commits.
There are 219 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 225 commits.
There are 225 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v7.17.0Added
Fixed
Changed
CommitsThe new version differs by 251 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 34 commits.
There are 34 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 36 commits.
There are 36 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 50 commits.
There are 50 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v7.20.0Added
Fixed
Docs
Changed
CommitsThe new version differs by 77 commits.
There are 77 commits in total. See the full diff |
The devDependency eslint-plugin-react was updated from
7.11.1
to7.12.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Release Notes for v7.12.0
Added
no-typos
: Support createClass (#1828, @alexzherdev)jsx-indent
: addcheckAttributes
option for JSX attribute indentation (#2086, @jomasti)propWrapperFunctions
setting values (#2065, @jomasti)jsx-fragments
rule to enforce fragment syntax (#1994, @alexzherdev)jsx-no-literals
: print node value in warning message (#2008, @jlgonzalezdev)Fixed
jsx-max-depth
: Fix depth of JSX siblings in a JSXEpressionContainer (#1824, @alexzherdev)no-array-index-key
: fix in React.Children methods (#2085, @himynameisdave)no-unused-state
: handle functional setState (#2084, @jomasti)no-deprecated
: Disable legacy lifecycle methods linting for now (#2069, @sergei-startsev)forbid-foreign-prop-types
: ensureallowInPropTypes
option applies to class fields (#2040, @Sheile)jsx-wrap-multilines
: catch single missing newlines (#1984, @MrHen)jsx-first-prop-new-line
: Fix for parsers (like TypeScript) (#2026, @HauptmannEck)jsx-sort-comp
][]: Fix fixer in case of more than 10 props (#2012, @tihonove)no-unused-state
Don't depend on state parameter name ([#1829][], @alexzherdev)no-this-in-sfc
fix for class properties (#1995, @sergei-startsev)no-this-in-sfc
fix rule behavior for arrow functions inside a class field (#1989, @sergei-startsev)destructuring-assignment
: handle nested props usage (#1983, @alexzherdev)sort-prop-types
: fix string property order (#1977, @metreniuk)jsx-no-target-blank
: don’t crash when there’s no value (#1949, @ljharb)prop-types
,no-unused-prop-types
: better handle object spread (#1939, @alexzherdev)Changed
jsx-fragments
: improve message text (#2032, @alexzherdev)no-unsafe
: handle all unsafe life-cycle methods (#2075, @sergei-startsev)require-default-props
: Change error message naming from singular defaultProp to plural defaultProps (#2064, @jseminck)propTypes
detection (#1946, @alexzherdev)defaultProps
detection (#1942, @alexzherdev)propTypes
detection (#2001, @alexzherdev)no-did-mount-set-state
,no-did-update-set-state
,no-will-update-set-state
: fix docs URLs (#2090, @JBallin)jsx-sort-props
: Fix small mistake (#2044, @dimitarnestorov)no-unescaped-entities
: add more escape examples (#2015, @stevemao)display-name
: mention defaultignoreTranspilerName
value (#2002, @OliverJAsh)jsx-no-target-blank
: Add full example (#1988, @atomcorp)jsx-no-target-blank
.md (#1953, @brunocoelho)require('babel-eslint')
from tests (#2004, @sergei-startsev)prop-types
: Add tests for prop-types destructuring (#2029, @sstern6)display-name
: add false positive component detection for destructured createElement (#1098, @arian)Commits
The new version differs by 127 commits.
a83d65c
Update CHANGELOG and bump version
0c6160e
[Dev Deps] update
coveralls
,babel-eslint
,typescript
cd6c8e6
[Deps] update
resolve
d2b5b73
Merge pull request #1828 from alexzherdev/1721-no-typos-create-class
e747459
[Tests] remove node 5/7/9, add node 11
b33ae84
Merge pull request #1098 from arian/createElement-display-test
84be80a
Merge pull request #1824 from alexzherdev/1762-jsx-max-depth-false-positive
a442067
Merge pull request #2029 from sstern6/issue1422
7d07c37
Merge pull request #2032 from alexzherdev/jsx-fragments-message
8c6a8e2
Merge pull request #2089 from jomasti/feature/support-react-forwardref-memo
14451d4
Merge pull request #2085 from himynameisdave/issues/2083
8be52c7
📝 Addresses CR comments
f7e3121
Merge branch 'master' of https://github.com/yannickcr/eslint-plugin-react into issues/2083
77e3fd0
Merge pull request #2090 from JBallin/no-method-set-state-docs-url
7da9e0d
Fix noMethodSetState docsUrl's
There are 127 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: