From e2faac1df033279cab70d75fe51fccffc1c03bd7 Mon Sep 17 00:00:00 2001 From: Arthur Dias Date: Sat, 30 May 2020 00:28:02 -0300 Subject: [PATCH] Docs: On maxEOF with eol-last (fixes #12742) Added an explanation on how and why maxEOF should be set to 0 to work with the eol-last rule. --- docs/rules/no-multiple-empty-lines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rules/no-multiple-empty-lines.md b/docs/rules/no-multiple-empty-lines.md index 1944dba5700..b25fb426984 100644 --- a/docs/rules/no-multiple-empty-lines.md +++ b/docs/rules/no-multiple-empty-lines.md @@ -97,4 +97,4 @@ If you do not care about extra blank lines, turn this off. ## Regarding the Airbnb JavaScript Style Guide `eol-last` rule -If you wish to use the Airbnb style guide rule regarding ending files with a single newline character (`eol-last`) with this rule, `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. \ No newline at end of file +If you wish to use the Airbnb style guide rule regarding ending files with a single newline character (`eol-last`) with this rule, `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.