-
Notifications
You must be signed in to change notification settings - Fork 532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing config to CLI causes assertion error #150
Comments
DanPurdy
added a commit
to DanPurdy/sass-lint
that referenced
this issue
Sep 10, 2015
Snugug
added a commit
that referenced
this issue
Sep 11, 2015
Fix CLI custom config assertion error #150
DanPurdy
added a commit
to DanPurdy/sass-lint
that referenced
this issue
Sep 11, 2015
bgriffith
added a commit
that referenced
this issue
Sep 12, 2015
Hotfix Master - Fix CLI custom config assertion error #150
donabrams
pushed a commit
to donabrams/sass-lint
that referenced
this issue
Nov 19, 2015
donabrams
pushed a commit
to donabrams/sass-lint
that referenced
this issue
Nov 19, 2015
Fix CLI custom config assertion error sasstools#150
donabrams
pushed a commit
to donabrams/sass-lint
that referenced
this issue
Nov 19, 2015
donabrams
pushed a commit
to donabrams/sass-lint
that referenced
this issue
Nov 19, 2015
Hotfix Master - Fix CLI custom config assertion error sasstools#150
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the CLI and
--config
an assertion error is generated if you callsass-lint
from a directory that doesn't include a.sass-lint.yml
file or apackage.json
with a config file specified within.Have a working fix ready to go, will just have a look at adding some tests
The text was updated successfully, but these errors were encountered: