Swig task that checks for possible issues in your code base.
Meant to be used via the Swig CLI, just run:
You can also instruct the CSS linter to use a different engine (default is an ancient version of Lesshint), namely Stylelint, like so:
swig lint --use-stylelint
You can also instruct the linter to look at a specific source folder
swig lint --src /web/web-blah/target
In this case you shall provide the linter a
.stylelintrc.yml file with the necessary Stylelint
By using Stylelint you can now also specify files to ignore (previously not possible), using the
.stylelintignore config file, which uses a
- Add more helpful information on the README (like list of JS/CSS rules) and how to override them.