-
-
Notifications
You must be signed in to change notification settings - Fork 6
Sorting CSS parsing error #36
Comments
That's odd, could you try re-installing the package? |
Yes, but same results. Maybe the accent in the route could be the culprit? |
🤔 shouldn't be, could you check if the file and enclosing directories exist? |
I reinstalled and is solved. Don't know why it happened, but now it's everthing ok. BTW could it be possible in future releases add an option for sort selection, or for avoid the sorting of some selectors? I accustom to place comments above the @font-face selector, and the plugin sends them to the bottom... |
Sorting the selected code might be a good addition to the plugin. However it shouldn't move the comments like that in the first place, could you give example CSS input, output and expected output? |
|
I found the culprit and will push the fix soon. The first comment is not detected as a newline comment because it's the first line in the file, if you add an empty line before it it will work as expected. It shouldn't touch comments outside declarations at all. |
I got that error when choose SMACSS or concentric CSS.
Thanks in advance
The text was updated successfully, but these errors were encountered: