operator-linebreak Changes

[BradMcGonigle]

After some discussion in Slack, it seems like most of us agree that having operator-linebreak set to before is not ideal in at least some cases.

Some like before for:

foo = 1
    + 2;

but not for

{
  foo
  && bar.map(var => (
    <Component />
  ))
}

or

if (someCondition
    || otherCondition) {
}

We could use after but there are cases where some seem not like that either.

answer = everything ?
  42 :
  foo;

versus what some prefer

answer = everything
  ? 42
  : foo;

The answer might be some customization using none and overrides

I'm thinking the rule might look like:

/*eslint operator-linebreak: ["error", "before", { "overrides": { "&&": "after", "||": "after" }}]*/

What other overrides would we want?