[linter] Add diagnostic doc for eol_at_end_of_file lint
Due to how Markdown code blocks are rendered, there's not a great way to showcase the difference in extra new lines. So I went with inline comments indicating where the files end. Let me know if you think a different direction might work better. Thanks!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
// and the reported range is past the end of the content.I'm guessing that this is the important part.
If the only problem is the extra diagnostic in some cases, then we could use an `%ignore` directive to ignore that diagnostic. But the requirement to have a highlight range seems to be impossible to satisfy. (At least, without changing the lint. I suppose we could have it report on the (non-comment) token before the end-of-file token, and then there'd be text to highlight.)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This CL review appears to have been dropped.
Connie: can you take a look at the docs? I'm ok with the changes to the test if we're ready to land the text.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This CL review appears to have been dropped.
Connie: can you take a look at the docs? I'm ok with the changes to the test if we're ready to land the text.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
The analyzer produces this diagnostic when a non-empty Dart file
doesn't end with exactly one newline.
The file either doesn't end with a newline,
or it ends with more than one.The analyzer produces this diagnostic when a non-empty Dart file
doesn't end with a single newline.
This occurs when a file has no trailing newline,
or when it has multiple trailing newlines.
Because trailing newlines aren't visible in a code block,
the examples below use a comment to mark where the file ends.Trailing newlines aren't visible in rendered code blocks.
To make them clear, the examples below use comments to show
where each file ends.
The following code produces this diagnostic because
the file ends with more than one newline:
The following code produces this diagnostic
because the file ends with multiple newlines:
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Thanks for the suggestions! Applied :)
The analyzer produces this diagnostic when a non-empty Dart file
doesn't end with exactly one newline.
The file either doesn't end with a newline,
or it ends with more than one.The analyzer produces this diagnostic when a non-empty Dart file
doesn't end with a single newline.
This occurs when a file has no trailing newline,
or when it has multiple trailing newlines.
Done
Because trailing newlines aren't visible in a code block,
the examples below use a comment to mark where the file ends.Trailing newlines aren't visible in rendered code blocks.
To make them clear, the examples below use comments to show
where each file ends.
Done
The following code produces this diagnostic because
the file ends with more than one newline:
The following code produces this diagnostic
because the file ends with multiple newlines:
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Looks like I need another reviewer for the test update. Mind taking a look? Thanks!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[linter] Add diagnostic doc for eol_at_end_of_file lint
Due to how Markdown code blocks are rendered, there's not a great way to showcase the difference in extra new lines. So I went with inline comments indicating where the files end. Let me know if you think a different direction might work better. Thanks!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |