Rule idea: mixin-name-pattern, function-name-pattern

Or mixin-pattern, function-pattern to follow the existing stylelint rule naming conventions.

stylelint-scss already has a rule for placeholder names, the one for variable names is in a PR now. The subject rules are the ones missing. SCSS-lint has those (though in a format of one general naming rule for Sass stuff). I could take implementing them, seems not that hard.

The only question I have: should some general patterns like lowercase-underscore, etc. be imlpemented as predefined primary option values (like in SCSS-lint)? If yes, what predefined patterns would you recommend to use?

[jeddy3]

Does stylelint use default options in rules?

As you both spotted, there are no default primary options for stylelint rules. It was a conscience decision to both keeps the rules unopinionated and to mitigate having to deliberate on what the defaults options should be 😃

There’s no harm in documenting those regexs though in the READMEs though.

[jeddy3]

Any suggestions?

stylelint-scss-like 😃

Maybe this plugin should also handle edge cases for other parsers (LESS, postcss plugins)?

That sounds sensible. There probably won’t be much overlap with Less, but I think they’ll be plenty with postcss plugins (with the likes of precss and these language extensions). I think no longer relying on developer discipline by crafting your own processor is going to become more popular, and so supporting this approach might add a bit more longevity to this project.