Skip to content
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

Docs: On maxEOF with eol-last (fixes #12742) #13374

Merged
merged 6 commits into from Jun 11, 2020
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/rules/no-multiple-empty-lines.md
Expand Up @@ -94,3 +94,7 @@ var bar = 3;
## When Not To Use It

If you do not care about extra blank lines, turn this off.

## Using It With The `eol-last` Rule

If you wish to use this rule with the `eol-last` core rule regarding ending files with a single newline character, `maxEOF` should be set to 0, as an empty line is actually represented by two newline characters (`\n\n`). There is no empty line at the end of a file after the last `\n`, although editors may show an additional line.
mdjermanovic marked this conversation as resolved.
Show resolved Hide resolved