more formatting options

[paulirish]

the options at http://procssor.com/ pretty much capture the most common style differences between authors.
having those present would be awesome.

[ariya]

We'll slowly go there :)

Next in my TODO list is an option to split the selectors, each into its own line.

[mathiasbynens]

I’d like to see an option to automatically add ; after each declaration (even if the source file didn’t have one). So…

.menu{color:red} .navigation{background-color:#333}

…which currently beautifies into:

.menu {
    color: red
}

.navigation {
    background-color: #333
}

…would become:

.menu {
    color: red;
}

.navigation {
    background-color: #333;
}

[ariya]

Automatic semicolon: commit 959c17c.

[mathiasbynens]

An option to add a space after each comma that separates multiple values or selectors would be neat, too. (Or maybe 1 space should be the default?)

E.g.

.foo,.bar{font-family:foo,bar,baz}

…would then beautify into:

.foo, .bar {
  font-family: foo, bar, baz;
}

Perhaps the “space character” after a comma should be a separate setting, as some people like to use a line break instead of a good o’ U+0020 there, e.g.:

.foo,
.bar {
  font-family: foo, bar, baz;
}

[mathiasbynens]

Similar feature request: add space before the parens that start a media query expression, and after each semicolon inside a media query expression that separates a property from a value. E.g.

@media(min-width:30em){x{foo:bar}}

…currently beautifies into:

@media(min-width:30em) {
  x {
    foo: bar;
  }
}

…but it could be:

@media (min-width: 30em) {
  x {
    foo: bar;
  }
}

[mishanga]

Guys, you are welcome to https://github.com/csscomb/csscomb.js