51369b610e
When an include is not surrounded by empty lines, its content is inlined on the same line as the adjacent content. That can lead to broken tags and other display issues. This PR fixes all such includes and introduces a validation step that forbids introducing the same problem again.
29 lines
567 B
Plaintext
29 lines
567 B
Plaintext
== Why is this an issue?
|
|
|
|
Some tools such as Git work better when files end with an empty line. This rule simply generates an issue if it is missing.
|
|
|
|
|
|
For example, a Git diff looks like this if the empty line is missing at the end of the file:
|
|
|
|
----
|
|
+class Test:
|
|
+ pass
|
|
\ No newline at end of file
|
|
----
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
include::../message.adoc[]
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
include::../comments-and-links.adoc[]
|
|
|
|
endif::env-github,rspecator-view[]
|