Only allow one blank line between blocks and at EOF
See original GitHub issueCurrently, the style.js enforces at most two lines:
// disallow multiple empty lines
'no-multiple-empty-lines': [2, {'max': 2}],
Should this follow this suggestion to enforce the max blank line to only 1?
Besides, this will affect the allowed blank line at the end of the file, too.
Issue Analytics
- State:
- Created 8 years ago
- Comments:12
Top Results From Across the Web
In ansible how to add a block of text at end of a file with a ...
This works 99%. The only issue is it adds the empty line at the end of file when the mark does not exists...
Read more >padding-line-between-statements: Missing functionality ...
no-multiple-empty-lines already handles empty lines at the beginning of files, but it can't handle the case where there is a comment at the ......
Read more >sed script to print lines between the last occurence of a pattern ...
Using the stream editor sed , we detect the pattern record and from there on skip the line and loop until the next...
Read more >no-multiple-empty-lines - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >Handy one-liners for SED
Output file # should contain no more than one blank line between lines of text. ... each line of file, but only print...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@dsernst You’re right! I had an outdated eslint version installed globally. I removed it and got rid of the error. Thank you very much!
@paulintrognon: If I remember correctly, there was a problem with my editor using globally installed package versions that were very out-of-date. I believe
nvm
was also making the issue worse by obfuscating my global npm installs.Once I removed all the old versions that were globally installed, both within
nvm
node-version-specific directories and outside, the issue went away.Hope this helps.