Skip to content
This repository was archived by the owner on Aug 7, 2023. It is now read-only.

Commit 2bc61b6

Browse files
committed
Update Changelog and documentation
1 parent 409960a commit 2bc61b6

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

CHANGELOG.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
## 1.5.0
2+
- Allows the inclusion of files with extra extensions such as 'file.scss.liquid'
3+
- Updated to Atom linter ^5.0.1
4+
- Includes eslint updates for development
5+
16
## 1.4.3
27
- Force latest version of sass-lint 1.7.0
38
- Update a few dependencies

README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,13 @@ There are three options you can configure either within the plugin or by editing
4646

4747
* `globalSassLint` This allows you to specify that you want to use your globally installed version of `sass-lint` (`npm install -g sass-lint`) instead of the version bundled with `linter-sass-lint`.
4848

49+
### Extra File Extensions
50+
51+
This plugin will attempt to lint a file with framework specific file extensions on top of the usual `.scss` and `.sass` extensions such as with shopify's `.scss.liquid` extension as long as you still include `.scss` or `.sass` somewhere in the file, you must also ensure that the Atom grammar scope for that file is set to either SCSS or Sass depending on which it corresponds to.
52+
53+
This does not mean that sass-lint will be able to definitely parse any sort of non standard SCSS or Sass code and if you use any platform specific code in the file it will almost definitely produce a parse error. Sass-lint will not be moving to support any use of non standard language outside of the Sass spec.
54+
55+
4956
### Contributing
5057

5158
Contributions, suggestions and fixes are more than welcome.

0 commit comments

Comments
 (0)