Bug: `array-element-newline` fails when `multiline` = `true`

Tell us about your environment

• ESLint Version: 4.3.0
• Node Version: *
• npm Version: *

What parser (default, Babel-ESLint, etc.) are you using? I had this happen locally, but I’ve been able to duplicate it using http://eslint.org/demo

Please show your full configuration:

Configuration

{
  rules: {
    "array-element-newline": [ "error", { "multiline": true } ]
  }
}

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

var blah = [
  0,
  1
];

What did you expect to happen? array-element-newline rule should succeed

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

The evaluated to a failure.

Output:

4:5 - There should be no linebreak here. (array-element-newline)

---

This can be easily reproduced if you go to http://eslint.org/demo, uncheck all rules, and insert the following text into the input box:

/*eslint array-element-newline: ["error", { "multiline": true }]*/

var blah = [
  0,
  1
];

[bsara]

Wow, I didn’t notice that at all. Sorry to bug you guys with this.

Perhaps multiline should be renamed to multiline-element to avoid confusion. It actually took reading the doc a few times before I really caught the part that says “if there are line breaks inside elements”.

Also, a multi-line option that enforces when any element is on a newline would be useful.

[richardpringle]

So… I might just be going crazy here but I swear you used to be able to enforce a rule where elements cannot overlap.

The most common case (maybe the only case) that I’m looking to solve is as follows:

const arr = [{
    hello: 'world'
  }, {
    foo: 'bar'
}]

What I would like to see is the ability to enforce that all array elements either share a single line or that no elements share lines. An oversimplification of this is that every line in a multiline array should end with a comma (except the last, depending on comma dangle).