Update dependency eslint-plugin-react to version 6.10.0

[renovate-bot]

This Pull Request updates dependency eslint-plugin-react from version 6.9.0 to 6.10.0

Changelog

6.10.0 / 2017-02-15

• Update CHANGELOG and bump version
• [Fix] jsx-indent with tabs (fixes #1057)
• Merge pull request #890 from kentor/forbid-elements
  Add forbid-elements rule
• Merge pull request #946 from BarryThePenguin/no-unused-prop-types-in-jsx
  detect used props in jsx
• Merge pull request #882 from kentor/jsx-max-props-per-line-updates
  Jsx max props per line updates
• Merge pull request #1055 from iancmyers/icm-forbid-foreign-prop-type
  Add forbid-foreign-prop-types rule
• Add forbid-foreign-prop-types rule
  People may want to use babel-plugin-transform-react-remove-prop-types
  to remove propTypes from their components in production builds, as an
  optimization. The `forbib-foreign-prop-types` rule forbids using
  another component's prop types unless they are explicitly
  imported/exported, which makes that optimization less prone to error.
  Fixes #696
• Merge pull request #1062 from dguo/patch-2
  Fix no-array-index-key typo
• Fix no-array-index-key typo
• Add new rule: forbid-elements
  May specify a list of forbidden elements and a custom reporting message
• Merge pull request #1051 from yannickcr/void-dom-elements-no-children
  Add void-dom-elements-no-children rule
• jsx-max-props-per-line: Use json format in docs
  To be consistent with the "Rule Options" section and other docs
• fix comments
• detect used props in jsx
  fixes #885
• jsx-max-props-per-line: Add additional test cases
  Make sure it works when a prop is on the same line as the start line of
  the tag, as well as with spread props that spans multiple lines.
• jsx-max-props-per-line: Add `when` option
  If `when` is set to `multiline`, then this rule skips checking entirely
  if the jsx opening tag is a single line.
  Defaults `when` to `always` which is the current behavior.
• jsx-max-props-per-line: Fix when prop spans multiple lines
  In this patch we now consider props to be on the same "line" if the line
  of where one prop ends matches the line of where the next prop begins.
  e.g.
  ```
  <App foo={{
  }} bar />
  ```
  `foo` and `bar` are now considered to be on the same line. Previously,
  we would only look at the line in which the prop begins.
• Merge pull request #1045 from CarlRosell/fix-require-default-props
  Test for require-default-props rule filter of undefined exception
• Add test for 'type Props = any' for require-default-props rule
• Add void-dom-elements-no-children rule
  There are some HTML elements that are only self-closing (e.g. `img`,
  `br`, `hr`). These are collectively known as void DOM elements. If you
  try to give these children, React will give you a warning like:
  > Invariant Violation: img is a void element tag and must neither have
  > `children` nor use `dangerouslySetInnerHTML`.
  This rule prevents this from happening.
  Since this is already a warning in React, we should add it to the
  recommended configuration in our next major release.
  Fixes #709
• Change readme syntax from json -> json5
  I didn't notice there were comments here.
• Merge pull request #1050 from yannickcr/js-jsx-docs
  Improve syntax highlighting of code snippets
• Improve syntax highlighting of code snippets
  Using the jsx tag on the fenced code blocks will instruct GitHub to use
  JSX syntax highlighting, which will usually be better.
• [Fix] node < 4 lacks `Array.prototype.find`
• Merge pull request #958 from Jorundur/patch-1
  "jsx-indent" -> "react/jsx-indent"
• Merge pull request #979 from markus101/jsx-sort-props-no-sort-alphabetically
  jsx-sort-props noSortAlphabetically option
• Merge pull request #1011 from jomasti/fix-996
  Check for createElement being called from React
• Merge pull request #1041 from EvNaverniouk/976
  Minor documentation updates for no-unused-prop-types rule for issue 976
• Merge pull request #1018 from wyze/fix-require-default-props-with-flow-assignment
  Fix `require-default-props` rule when using Flow type from assignment
• Minor documentation updates for no-unused-prop-types rule for issue 976
• [Tests] require tests to pass down to node 0.10; add node 7
• [Tests] fix tests so they pass with eslint 2.
• [Tests] shim `Object.assign` in tests so that `babel-eslint` works in older nodes.
• [Fix] restore older eslint compat by using `object.assign` instead of `Object.assign`
• [Fix] `style-prop-object`: do not warn with explicit `null` or `undefined` var style props.
  Per style-prop-object does not allow null jsx-eslint/eslint-plugin-react#812 (comment)
• Add --save-dev to npm install commands in readme
  Added --save-dev to npm install commands in readme
• Fix require-default-props crash with babel-eslint@5 (fixes #1029)
• Fix `require-default-props` rule when using Flow type from assignment
• Add support for nextProps to prop-types (fixes #814)
• Update prefer-stateless-function documentation
  show context in pure component for clarity
• Merge pull request #1023 from wKich/issue-1021
  Fix no-array-index-key rule exception
• Fix no-array-index-key rule exception
• show context in pure component for clarity