Rules explicitly turned off if not listed ESLint style

[lozandier]

It's not clear if rules not present in sass-lint.yml files are turned off automatically (ESLint 1.0 style) or not.

With early runs of gulp-sass-lint, that does not seem to be the case; for codebases that have both Sass & SCSS litn files, it seems there's issues propagating from gonzales-pe unless trailing-semicolon is explicitly set to 0 rather than merely omitting the rule altogether:

Seemingly any rule not listing in the sass-lint.yml should be turned off (severity of 0) since that's the clearest way for users of the plugin-in to communicate they are not concerned of that rule being applied to their codebase.

Overtime, it can be more work for them to apply rules they don't care about in their codebase than the rules they care about as rules become simultaneously more useful & complex.

[Snugug]

I originally had it so that user config overrode the default configuration instead of merging, but found that if someone only wanted to change indentation, for instance, they needed to be explicit with their whole configuration.

One option is to not have anything configured by default. Other thoughts?

[lozandier]

That sounds very sensical to me actually; for the ESLint-style behavior, perhaps it's a flag?

I see this project taking off fast and that can be a pretty dramatic change of behavior all of a sudden…