We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
sass-lint@1.7.0 linter-sass-lint@1.5.0 for Atom
url-quotes: 1
background: #ffffff url(./img/image.jpg) center center;
The error position points to either the first character after the opening paren (the dot '.'):
background: #ffffff url(./img/image.jpg) center center; ^
or to the whole paren contents, if range is possible:
background: #ffffff url(./img/image.jpg) center center; ^^^^^^^^^^^^^^^
The error position points to letter 'g' in '.jpg':
60:41 warning Quotes around URLs are required url-quotes
I tried webpack plugin, https://github.com/alleyinteractive/sasslint-webpack-plugin – no difference.
The text was updated successfully, but these errors were encountered:
Thanks for the report! I think this is valid and it's super easy to fix 👍
Sorry, something went wrong.
Hmm this should of closed when #713 was merged..
@bgriffith @DanPurdy Thanks! When do you think this will get to npm?
No branches or pull requests
What version of Sass Lint are you using?
sass-lint@1.7.0
linter-sass-lint@1.5.0 for Atom
Please include any relevant parts of your configuration
What did you do? Please include the actual source code causing the issue.
What did you expect to happen?
The error position points to either the first character after the opening paren (the dot '.'):
or to the whole paren contents, if range is possible:
What actually happened? Please include any error messages given to you by Sass Lint.
The error position points to letter 'g' in '.jpg':
If you're using a IDE plugin have you tried the CLI too?
I tried webpack plugin, https://github.com/alleyinteractive/sasslint-webpack-plugin – no difference.
The text was updated successfully, but these errors were encountered: