New rules: block-opening-brace-before and -after about stylelint

[davidtheclark]

For this and most of the other whitespace-related ones --- do we want to leave the whitespace entirely open-ended, or just give the keyword options "space" and "newline"? Do we imagine scenarios when somebody might want to do something weird like use 4 spaces, a tab, 2 newlines, a carriage return, etc.? It would certainly simplify things if we only had "space" and "newline" as keywords for the options ... Thoughts?

[davidtheclark]

Disclosure: I'm kind of leaning towards keywords myself, because it makes things much simpler and I have this sense that anything other than space/newline is a serious edge case ...

[MoOx]

Go simple indeed !

[jeddy3]

Agreed.

[davidtheclark]

I'm throwing out the single- vs multi-line distinction for this rule unless somebody requests it. It would add significant complexity that I would rather not build in for a questionable use-case. The only use-case I can think of is a styleguide that wants this:

body { color: pink; }

a
{
  color: pink;
  background: orange;
}

But I think pretty much everybody would prefer consistency before that brace ... either:

body { color: pink; }

a {
  color: pink;
  background: orange;
}

or:

body
{ color: pink; }

a
{
  color: pink;
  background: orange;
}

... since I think the only reason to have a newline before the brace is to clearly demarcate the selector

[jeddy3]

Agreed. I think you're totally right to avoid questionable use-cases until they are request.

Lets keep things as simple as we can to begin with :)

[davidtheclark]

Done in 61512b4 and 4706ab1