Wrong output indentation in all messages if one message has a long multiline quote

What version of ESLint are you using?

2.11.1

What parser (default, Babel-ESLint, etc.) are you using?

default

Please show your full configuration:

{
  "root": true,

  "extends": [
    "eslint:recommended",
    "airbnb-base"
  ],

  "parserOptions": {
    "ecmaVersion": 7,
    "sourceType": "script"
  },

  "env": {
    "browser": false,
    "es6": true,
    "node": true
  },

  "rules": {
    "arrow-parens": [2, "as-needed"],
    "eqeqeq": 2,
    "key-spacing": [2, { "beforeColon": false, "afterColon": true, "mode": "minimum" }],
    "no-console": 0,
    "no-eq-null": 2,
    "no-extra-parens": [2, "all"],
    "no-multi-spaces": 0,
    "no-unused-vars": 2,
    "no-use-before-define": [2, { "functions": false }],
    "quotes": [2, "single"],
    "spaced-comment": [2, "always", { "exceptions": ["/", "*"] }],
    "strict": [2, "global"],
    "unicode-bom": [2, "always"]
  }
}

What did you do? Please include the actual source code causing the issue.

const http = require('http');

http.request({
  // Param
  // Param
  // Param
}).on('response', response => {
  // Do something with response.
  // Do something with response.
  // Do something with response.
  // Do something with response.
  // Do something with response.
  // Do something with response.
  // Do something with response.
  // Do something with response.
  // Do something with response.
  // Do something with response.
}).on('error', error => {
  // Do something with error.
  // Do something with error.
  // Do something with error.
  // Do something with error.
  // Do something with error.
  // Do something with error.
  // Do something with error.
  // Do something with error.
  // Do something with error.
  // Do something with error.
}).end();

What did you expect to happen?

An output with readable indentation and alignment.

What actually happened? Please include the actual, raw output from ESLint.

Compare with the output after the last error fixed:

[ilyavolodin]

It looks like a bug that we should fix. However, I don’t think we should fix formatter itself, but instead we should modify newline-per-chained-call to not dump that much information into the error message.

[mysticatea]

Ah OK. Default allows 2 chained and disallows 3rd and later.