-
Notifications
You must be signed in to change notification settings - Fork 528
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
New Rule Proposal: Disallow multiple empty lines #1015
Comments
Hi sorry for the delay in getting back to you, had no free time it seems recently. I'd be happy to see a PR submitted for this. Thanks! |
I would love this too. |
Cool, great! I'll try to look into this this week & see if I can get something raised for it. |
I would love this as well. (: |
For anyone else who feel like they need this rule, I now have a fork where this rule is implemented: https://github.com/fiso/sass-lint You can try it out by changing your dependency import line to say I'd be happy to submit a PR for it but I feel like I'd want some eyes on my take before I do that, seeing as how I'm completely new to this codebase and all. |
FWIW my team has been using the forked version for a couple of weeks now and encountered no problems with it. |
There seems to be some overlap between this suggested rule and the one suggested in #1073. |
FWIW the rule I implemented in my fork (linked above) supports the suggestion from #1073 as well (optionally). |
@Potherca Yes that would make sense. As for the pull request, yes, I've been meaning to do that since forever. I keep putting it off since the checklist for submitting PRs to the project seems kind of daunting. But I'll make time for it. |
Hello,
I'd like to propose a rule to disallow multiple consecutive empty lines in a file. E.g.:
For JavaScript, we're using ESLint's no-multiple-empty-lines rule which allows for:
I'd be happy to try and submit a PR / test cases for same, but wanted to first check if it sounded like a feature others would want to.
Please let me know if I can give more relevant details.
Thanks!
Dave
The text was updated successfully, but these errors were encountered: