indent conflicts with react/jsx-closing-bracket-location

Tell us about your environment

• ESLint Version: 5.16
• Node Version: 11.4.0
• yarn Version: 1.9.4

What parser (default, Babel-ESLint, etc.) are you using? @tylescript-eslint/parser

Please show your full configuration:

.eslintrc:

module.exports = {
  env: {
    'jest/globals': true
  },
  extends: [
    'airbnb',
    'plugin:@typescript-eslint/recommended',
  ],
  globals: {
    'document': true,
    'window': true,
  },
  parser: '@typescript-eslint/parser',
  parserOptions: {
    ecmaFeatures: {
      jsx: true,
    },
    project: './tsconfig.json',
  },
  plugins: ['@typescript-eslint', 'jest'],
  rules: {
    'indent': 'off',
    '@typescript-eslint/indent': [
      'error',
      2,
      {
        'ignoredNodes': ['JSXElement *'],
        'SwitchCase': 1,
      },
    ],
  },
  settings: {
    'import/extensions': [
      '.js',
      '.jsx'
    ],
    'import/resolver': {
      webpack: {
        config: 'webpack.common.js',
      }
    }
  },
};

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

1. Clone this repo.
2. run yarn
3. run yarn build:dev

What did you expect to happen?

No errors. Aligning the closing bracket should not cause an indent error. I am stating that the indent rule should be ignored for JSX Elements. Note that indenting the closing bracket will conflict with the react/jsx-closing-bracket-location rule.

sampleComponent.jsx:

import React from 'react';

const SampleComponent = () => (
  <h
    custom-attr-one="1"
    custom-attr-two="2"
    custom-attr-three="3"
  > // <- causes failure
    custom header
  </h>
);

export default SampleComponent;

error:

ERROR in ./src/sampleComponent.jsx
Module build failed (from ./node_modules/eslint-loader/index.js):
Module failed because of a eslint error.

/Users/jemery/dev/typescript-eslint-debug/src/sampleComponent.jsx
  8:1  error  Expected indentation of 4 spaces but found 2  @typescript-eslint/indent

✖ 1 problem (1 error, 0 warnings)
  1 error and 0 warnings potentially fixable with the `--fix` option.

 @ ./src/index.jsx 4:0-48 5:27-42
 @ multi babel-polyfill ./src/index.jsx
error Command failed with exit code 2.

ESLint Demo

Are you willing to submit a pull request to fix this bug? Yes

[platinumazure]

What happens if you configure your ignored nodes to include JSXElement as well (not just JSXElement *)?

[andrewjrhill]

As suggested by OliverSieweke, the following "indent" configuration is working for me:

"rules": {
    "indent": ["error", 4, {"ignoredNodes": ["JSXElement", "JSXElement *"]}],
}