spudly / strip-brackets Goto Github PK

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

6.1.2 / 2018-10-05
[fix] Add link-type styling recommendation to anchor-is-valid #486
[fix] label-has-for: textareas are inputs too #470

The new version differs by 12 commits.

• c538d35 6.1.2
• ea964b1 Update changelog
• 43d1d94 Add link-type styling recommendation to anchor-is-valid
• 71819a0 [Docs] accessible-emoji: plural of emoji is emoji
• 4a0608b [Docs] label-has-associated-control: update label id
• 9957219 [Tests] temporarily allow node 4 + eslint 4 to fail
• 969ce6d [Dev Deps] add missing dev dep
• 1be1744 [Tests] use nvm install-latest-npm
• 9103c7a [Tests] add additional test case for #474
• bbad58a Merge pull request #471 from ljharb/textarea
• 47633fb [Fix] label-has-for: textareas are inputs too
• c1bf3c1 Update aria-props.md to link to the correct doc

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

🔗 Changelog

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Added

• no-typos: Support createClass (#1828, @alexzherdev)
• Support detecting React.forwardRef/React.memo (#2089, @jomasti)
• jsx-indent: add checkAttributes option for JSX attribute indentation (#2086, @jomasti)
• Change allowed propWrapperFunctions setting values (#2065, @jomasti)
• add jsx-fragments rule to enforce fragment syntax (#1994, @alexzherdev)
• Support "detect" option for React version setting (#1978, @alexzherdev)
• Support shorthand fragment syntax in many rules (#1956, @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)
• version errors should log to stderr, not stdout (#2082, @ljharb)
• no-deprecated: Disable legacy lifecycle methods linting for now (#2069, @sergei-startsev)
• ensure that react and flow versions can be numbers (#2056, @ljharb)
• forbid-foreign-prop-types: ensure allowInPropTypes 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)
• [Refactor] Extract used propTypes detection (#1946, @alexzherdev)
• [Refactor] Extract defaultProps detection (#1942, @alexzherdev)
• [Refactor] Extract required propTypes detection (#2001, @alexzherdev)
• [Docs] no-did-mount-set-state, no-did-update-set-state, no-will-update-set-state: fix docs URLs (#2090, @JBallin)
• [Docs] Remove statement on GC in jsx-no-bind (#2067, @rickhanlonii)
• [Docs] jsx-sort-props: Fix small mistake (#2044, @dimitarnestorov)
• [Docs] no-unescaped-entities: add more escape examples (#2015, @stevemao)
• [Docs] display-name: mention default ignoreTranspilerName value (#2002, @OliverJAsh)
• [Docs] jsx-no-target-blank: Add full example (#1988, @atomcorp)
• [Docs] Update jsx-no-target-blank.md (#1953, @brunocoelho)
• [Changelog] fix "Ignore class properties" contributor (#1941, @alexzherdev)
• [Tests] Remove redundant require('babel-eslint') from tests (#2004, @sergei-startsev)
• [Tests] prop-types: Add tests for prop-types destructuring (#2029, @sstern6)
• [Tests] display-name: add false positive component detection for destructured createElement (#1098, @arian)

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

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

The new version differs by 34 commits.

• 767f01a bump to v2.15.0
• 038d668 bump webpack resolver to v0.11.0
• 20a8f3b bump utils to v2.3.0
• 1e4100d changelog note for #1261
• 548ea02 added support for argv parameter of webpack`s config-as-a-function (#1261)
• fcf2ce7 Merge pull request #1254 from ljharb/travis
• 64d9be7 allow_failures for dicey Node/ESLint intersection
• 73080d0 dep-time-travel: use older versions of dependencies
• 05c3935 repair no-deprecated for ESLint* 5
• 10c9811 node 4 fix for test util
• f165237 ah geez, bumping babel-eslint breaks no-amd/no-cjs
• acfb6e9 jk, test against eslint 2/3 but skip Typescript tests.
• b686f9d drop ESLint 2/3 from Travis/Appveyor
• cf1f6f4 [Deps] update debug, eslint-import-resolver-node, has, lodash, minimatch, resolve
• d290a87 [Dev Deps] update babylon, coveralls, eslint-import-resolver-typescript, gulp, linklocal, nyc, redux, rimraf, sinon, typescript-eslint-parser

There are 34 commits in total.

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.