@SandwichTech Thanks for the request.

To confirm, you'd like:

• all rule-sets to be on a single line (regardless of how declarations they contain)
• all at-rules to be on multiple lines

Is that correct?

If so, we can add ignore options to the block-opening-brace-*-after rules:

• ignore: ["rules"] to block-opening-brace-newline-after
• ignore: ["at-rules"] to block-opening-brace-space-after

You'd then be able to configure the rules like so:

{
  "rules": {
    "block-opening-brace-newline-after": ["always", { "ignore": ["rules"] } ],
    "block-opening-brace-space-after": ["always", { "ignore": ["at-rules"] } ],
  }
}

@jeddy3 I appreciate the quick response.

1. Yes, declarations are all on one line. However, there is a newline after commas between selectors ('selector-list-comma-newline-after': 'always')
2. Yes, all at-rules are multi-line.

Those options should be what you need then.

It should just be the case of wrapping this line in a conditional:

Like so:

if (!optionsMatches(options, 'ignore', 'rules') {
  root.walkRules(check); 
}

And updating the options validator (see a similar rule to how this is done).

Then doing the same for the other rule, but ignoring at-rules instead of rules.

I've labelled the issue as ready to implement. Please consider contributing if you have time.

There are steps on how to add a new option in the Developer guide.

I would like to take this one.