linter-sass-lint

This linter plugin for Linter provides an interface to sass-lint. It will be used with files that have the “Sass” or “SCSS” syntax.

sass-lint is a node only sass linter and isn't related to scss-lint.

Installation

You'll need to have Linter installed to use this plugin

The current latest version of sass-lint comes bundled with this plugin but if you'd like to install it manually you can follow the instructions here.

Plugin installation

apm install linter-sass-lint

.sass-lint.yml

A .sass-lint.yml config file is required for this linter. You can find an example of one here and documentation on how to configure this and each of the rules here.

By default this plugin will search up the directory tree for this file, you can also specify a path to this config file in the plugin settings or in ~/.atom/config.cson file. Usually you would place this config file in your projects root and keep it under version control too.

You can use the noConfigDisable option to prevent any attempts at linting (and the missing config error messages you will encounter) if a valid config is not found.

By default a config file found in the root of your currently open project will take preference over a config file specified with the configPath option.

Settings

There are three options you can configure either within the plugin or by editing your ~/.atom/config.cson file.

executablePath - this is the path to a locally installed sass-lint package (by default the latest version of sass-lint version will be included with and used by this plugin when it is installed).
configPath - this is path to a .sass-lint.yml config file, this should only be used if you'd like to specify a global config file rather than rely on a project config file in the root of your project.
noConfigDisable - Enable to prevent any linting if a valid config file (.sass-lint.yml) is not found in the project root.

Contributing

Contributions, suggestions and fixes are more than welcome.

Please read the Contribution Guidlines

A general sense of the guidelines can be found below.

Indentation is 2 spaces.
All code should pass the coffeelinter linter, the config of which is included in this repository (npm-test).
the .editorconfig file should be used to ensure a consistent style info here

General contribution guidelines apply

Fork the plugin repository
Create a feature/hotfix branch off of master
Lint your code npm-test
Commit and push the branch
Make a pull request

If you're unsure on whether your contribution will be required then please file an issue first and we can discuss it.