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
In Stylint version: 1.0.4 on OSX, Windows, ... Given: "colons": {"expect": "always", "error": true},
"colons": {"expect": "always", "error": true},
We get:
Error: unecessary colon found File: app/bundles/logged-site/logged-site.styl Line: 2: background: yellow;
Most probably because starting from line 19 in checks/colons.js we have:
var arr = line.split( ' ' ) if (... && arr[0].indexOf( ':' ) === -1) { colon = false }
So:
var arr = ' background: yellow'.split( ' ' ) // ["", "", "background:", "red"] // and colon becomes false
I think that the regression has appeared in 1bb2eee and there are no tests for untrimmed lines.
The text was updated successfully, but these errors were encountered:
i had a utility function that trims the lines that i wasn't using. 1.0.6 should resolve this
Sorry, something went wrong.
Seems to be working in 1.0.6.
awesome, closing out...
Hi
I found a weird issue with colon detection:
Code: .smart-image-gallery { .test2 { display: flex; flex-flow: column nowrap; justify-content: space-between; align-items: center; } }
Error:
Error: missing colon between property and value File: src/gallery.styl Line: 2: .test2 {
I found that if I rewrite '.smart-image-gallery' with just '.smart', I won't receive this error. Could you take a look?
No branches or pull requests
In Stylint version: 1.0.4 on OSX, Windows, ...
Given:
"colons": {"expect": "always", "error": true},
We get:
Most probably because starting from line 19 in checks/colons.js we have:
So:
I think that the regression has appeared in 1bb2eee and there are no tests for untrimmed lines.
The text was updated successfully, but these errors were encountered: