Pluggable Rules

[Snugug]

We should provide a way for end users to define and distribute rules as NPM packages that will be automatically picked up and be usable by Sass Lint

• Look to ESLint as model
• Recurse down dependency tree to find rules
• Create naming convention

[gajus]

I am happy to take responsibility of this, assuming everyone agrees with the proposed naming convention and implementation logic, #432.

[gajus]

Though, I am not happy that this has a milestone v2.0.0. This is not a breaking change.

[Snugug]

While this is not a breaking change, it's part of the suite of things we're going to be releasing in 2.0, which will have enough breaking changes that it will effect anything that touches the AST. We don't want to introduce something like this for a point version and then quickly deprecate all of that work for the changes we're introducing.

[glen-84]

Any news here? Is there no other way to add custom rules at the moment?

[kmiyashiro]

We don't want to introduce something like this for a point version and then quickly deprecate all of that work for the changes we're introducing.

I wouldn't consider 1.25+ years quickly deprecating something 😅 . Unless 2.0 is imminent, maybe pluggable rules can be considered as a 1.x feature? Is there a way to define custom rules without creating separate modules currently?