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.
47 lines
995 B
Plaintext
47 lines
995 B
Plaintext
== Why is this an issue?
|
|
|
|
Jump statements, such as ``++CHECK++`` and ``++CONTINUE++`` let you change the default flow of program execution, but jump statements that direct the control flow to the original direction are just a waste of keystrokes.
|
|
|
|
=== Noncompliant code example
|
|
|
|
[source,abap]
|
|
----
|
|
LOOP AT myTable.
|
|
PERFORM form_open USING ...
|
|
CHECK retcode = 0.
|
|
...
|
|
perform form_close.
|
|
CHECK retcode = 0. "Noncompliant; whatever the result of the check, the loop will continue to the next iteration
|
|
ENDLOOP.
|
|
----
|
|
|
|
=== Compliant solution
|
|
|
|
[source,abap]
|
|
----
|
|
LOOP AT myTable.
|
|
PERFORM form_open USING ...
|
|
CHECK retcode = 0.
|
|
...
|
|
PERFORM form_close.
|
|
ENDLOOP.
|
|
----
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
include::../message.adoc[]
|
|
|
|
include::../highlighting.adoc[]
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
include::../comments-and-links.adoc[]
|
|
|
|
endif::env-github,rspecator-view[]
|