-
Notifications
You must be signed in to change notification settings - Fork 21
Doesn't Lint #45
Comments
Same here. Seems started to happen after recent Atom update. |
+1 |
OK, while troubleshooting another problem I found I have a /Users/bob/.rvm/gems/ruby-2.0.0-p247 that is a broken sym-link. When I re-pointed it to /Users/bob/.rvm/gems/ruby-2.0.0-p247@rails3, scss-lint began working. Maybe you guys have that problem, too? |
XML formatter was deprecated from scss-lint that's why https://github.com/brigade/scss-lint/releases/tag/v0.39.0 |
There's the Checkstyle formatter that returns XML, but it adds a gem depedency and didn't fix things for me. It would be smarter to use the JSON formatter instead. |
Yeah, scss-lint stopped working for me as well. Hope this gets fixed. |
Check this issue for something that fixed it for me: #39 |
Just a +1 on this; using the latest version of scss-lint makes this package not work due to the change indicated by @aniss . A workaround for now is to remove the old version ( |
Thanks @benschell. However, what got it working again, for me, was running Side note, I mentioned that the JSON formatter should be used instead. There is an open PR that already fixes this. @hd-deman Are you able to work on this package? Edit: Nevermind, using the old version of the gem doesn't work in Atom v0.210. I get Edit 2: See #39 for a current fix. |
#42 works for me. |
+1 #42 works! |
So I think I have a potential quickfix using the checkstyle plugin for scsslint, and also using a fix for the scss-lint binary path issue. Though, since there is no spec I am going to spend a day or two kicking the tires before submitting my pull request. But feel free to test my fork please https://github.com/AtomLinter/linter-scss-lint |
Hmm, didn't notice #42 till now, I'll give that a try. I would agree JSON would be the way to go. |
Is the new release with #42 is working for you guys? |
Isn't working for me right now, at least. :/ But I only tested it today, after getting the new release, so I don't know if I've done this right. |
The 1.0.5 release is not working. |
Not working for me:
|
It wasn't working at first, it was showing one error on the the top of the page. However, I was messing around with linter and gem versions and got it to work. I'm not exactly sure what the fix was, but try:
I'm using the latest linter and gem: linter@1.1.0 |
confirmed, that worked for me as well
update .atom/config.cson
|
The @calderas is not working for me. Does anyone gonna fix this? |
@davegomez try to run |
@davegomez It's hard to fix an issue which we can't reproduce. Ruby has too many configurations possible (rvbenv, rvm, plain ruby) it differs with systems too. |
The executable path is working, it doesn't matter if it takes it automatically or if you set the complete path manually. The issue is present with the latest version of the linter since you can use an older version and it works fine. I already try to read the code to see if I could figure it out, but I'm not a CoffeeScript developer and can't understand very well how the atom packages work. By the way, the linter launch a message about an unknown error at line one, so I suspect it could be a file parsing error or something like that. |
Running the latest version of the linter (1.0.5) and Atom (1.0.2) It throws two errors: “The linter binary 'scss-lint' cannot be found. “Failed to spawn command scss-lint. Make sure scss-lint is installed and on your PATH” Thank you. |
@quicoto That's not a bug, that's an error message. You can resolve your issue by installing the |
Fixed by #58 |
I don't get any errors thrown, nor do I get any linting. I'm not even sure where to look, now. I used to get errors about not finding scss-lint, but those have cleared up.
How can I tell why no linting is happening to .scss files?
The text was updated successfully, but these errors were encountered: