Make 'indent' rule configurable w.r.t ternary conditions

ESLint version 3.0.0, babel-eslint parser

Rule: http://eslint.org/docs/rules/indent

Problem: Ternaries can be formatted better when used for multi-line conditionals, ‘indent’ rule currently does not allow this.

Example of the formatting pattern:

const object = cond
  ? {
      foo: 'bar'
    }
  : {
      baz: 'qux'
    }

Notice how the braces line up and are easy to visually scan compared to this, which is what the ‘indent’ rule currently expects:

const object = cond
  ? {
    foo: 'bar'
  }
  : {
    baz: 'qux'
  }

This goes for parenthetical expressions, multi-line function calls, and array literals as well.

Solution: I propose a new option for ‘indent’ called "multilineTernary" that defaults to level 1 like the other opinionated ‘indent’ options, and which enforces the above pattern rather than the below.

[jonvuri]

If it’s a matter of time commitment, I’d be happy to make a pull request. It sounds like those who weighed in so far wouldn’t use this multi-line style to begin with, so changing the behavior of lines following infix-operator-begun lines wouldn’t affect them anyway. Can we instead have the discussion from the standpoint of assuming this style (which is valid), and then what indentation should be enforced for that style?

[idbartosz]

@Naoto-Ida Dirty fix is disabling rules with inline comments

/* eslint-disable indent */
const object = cond
  ? {
      foo: 'bar'
    }
  : {
      baz: 'qux'
    } 
/* eslint-enable */

I look forward for this indentation syntax, maybe in 2018 😅