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

Commit 7f84d7b

Browse files
committed
Update readme and prepare 1.6.0
1 parent 4d84997 commit 7f84d7b

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

CHANGELOG.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
1+
## 1.6.0
2+
- Adds `resolvePathsRelativeToConfig` to the config options to allow paths to be resolved relative to your config file rather than project root. Thanks to [@DirtyHairy](https://github.com/DirtyHairy)
3+
- The usual third party package updates
4+
15
## 1.5.0
26
- Allows the inclusion of files with extra extensions such as 'file.scss.liquid'
37
- Updated to Atom linter ^5.0.1

README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,8 @@ 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+
* `resolvePathsRelativeToConfig` This option allows you to choose to resolve file paths relative to your config file rather than relative to the root of your currently open project.
50+
4951
### Extra File Extensions
5052

5153
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.

0 commit comments

Comments
 (0)