-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
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
Add option to disable the warning for empty css files #84
Comments
Add a css comment in them ? |
if there is no option in plugin then I will comment empty file and to that I will have to check first which file is empty and which not. |
I mean you can add a comment in the empty file, not commenting the import usage. |
Yes. That can be done too. Thanks. Also I would suggestion that in error message instead showing the whole path from root, can be done in shorter way.
Later I would prefer if this plugin can have an option to disable this warning. |
PR are always welcome :) |
I'm not good in Javascript, but I will try to learn it and send. Jitendra Vyas On Sun, Sep 20, 2015 at 11:18 PM, Maxime Thirouin notifications@github.com
|
@MoOx Why did you add warning on empty? |
Because this might be an user "error". |
Usually it's just because user didn't add content yet. And I don't think this feature is useful. |
I already have people asking me why "it doesn't work" and where editing the wrong file. |
Let's keep it open for a time. |
PR welcome to add an option for this. We might change default behavior sometime, not now. |
I wish there were an option flag like
|
This comment was marked as off-topic.
This comment was marked as off-topic.
Thank you for adding this option. |
I have my own common project folder with lots of small css files. I have no problem if some partials are emply. I might add css to them later. Is there a way to disable the warning?
The text was updated successfully, but these errors were encountered: