Efficient CSS about scss-lint

[sds]

Hey @katgironpe, thanks for using scss-lint!

This is a great idea. We thought about it a while back, but at the time weren't sure about its practicality as it's possible it too would result in a lot of noise. Now that we've moved completely onto SCSS, we've noticed some clear patterns where deeply nested selectors (whether they're child or descendant combinators) not only result in poor performance, but are also a smell. The magic number for us seems to be 3, as in a depth > 3 is too deep.

Regarding the comment about typos/spaces, I would agree that it is not a valuable use of time to correct an existing codebase to such a style for the sake of doing so. At @causes we value consistency, especially when we can create an automated tool to enforce such a consistency for us, and think that this does indeed bring value.

However, if the more stylistic lints are bugging you, not to worry. We'll soon be releasing a configuration system that allows you to enable/disable particular lints.

Thanks for your comments and suggestions. We'll try to take a stab at this sometime this week.

[kathgironpe]

The stylistic lints are not bugging me. I do not disagree with anything the gem does so far.