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.
36 lines
798 B
Plaintext
36 lines
798 B
Plaintext
== Why is this an issue?
|
|
|
|
In JavaScript, the semicolon (``++;++``) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
|
|
|
|
|
|
=== Noncompliant code example
|
|
|
|
[source,javascript]
|
|
----
|
|
function fun() {
|
|
return // Noncompliant. ';' implicitly inserted at end of line
|
|
5 // Noncompliant. ';' implicitly inserted at end of line
|
|
}
|
|
print(fun()); // prints "undefined", not "5"
|
|
----
|
|
|
|
|
|
include::../compliant.adoc[]
|
|
|
|
|
|
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[]
|