-
Notifications
You must be signed in to change notification settings - Fork 37
Strange LESS file message #181
Comments
Can you upload the raw file? Does |
i can't get it to happen again. I will keep an eye out. |
Okay, marking as Unable to reproduce and closing for now. |
This happens when I create a new less file and attempt to create a new classname. The error is triggered just before typing the opening bracket. This also, does not show up when running stylelint through command line |
Managed to reproduce this intermittently from your steps @gregorywyz. Got the following stack trace which tells us that this is a bug in
Unfortunately |
Filed an issue there, hopefully it can be taken care of when somebody takes on that project again. |
@Arcanemagus @gregorywyz I've been given ownership of postcss-less and will be actively maintaining it for the foreseeable future. If you all can get me a file or line that produces an error consistently using the parsing methods shown here, I can probably debug it. Unfortunately I don't have a whole bunch of interest in debugging it through Atom, through the plugin system, and through the plugin itself 😄 |
@shellscape I'll see what I can do, it's an intermittent issue though so reproducing it out of that environment will likely be difficult. |
Also, I would much rather keep discussion over in shellscape/postcss-less#64 as the bug has nothing to do with this package's code. |
I see in shellscape/postcss-less#64 that this should be resolved on that end as well as in this linter. My linter-stylelint package is up to date but I'm still getting this error when writing a new selector. Is there something I'm missing or that isn't yet updated? |
@abea stylelint may not have updated to the version which has that fix, or the linter plugin may not be following the pattern of trapping that error as a user types. @Arcanemagus that's probably something this plugin will have to do, rather than the stylelint package - you may wish to reopen this one. |
Looks like |
I was editing my theme and got this:
The text was updated successfully, but these errors were encountered: