
Inline adoc files when they are included exactly once. Also fix language tags because this inlining gives us better information on what language the code is written in.
44 lines
998 B
Plaintext
44 lines
998 B
Plaintext
== Why is this an issue?
|
|
|
|
Shared coding conventions allow teams to collaborate efficiently, and consistently spaced code has a strong impact on readability. This rule checks that the number of spaces between a data item's level and its name are consistent.
|
|
|
|
|
|
=== Noncompliant code example
|
|
|
|
[source,text]
|
|
----
|
|
01 StudentDetails.
|
|
05 StudentId PIC 9(7). *< Noncompliant
|
|
05 StudentName.
|
|
07 FirstName PIC X(10).
|
|
07 MiddleInitial PIC X. *< Noncompliant
|
|
07 Surname PIC X(15). *< Noncompliant
|
|
----
|
|
|
|
|
|
=== Compliant solution
|
|
|
|
[source,text]
|
|
----
|
|
01 StudentDetails.
|
|
05 StudentId PIC 9(7).
|
|
05 StudentName.
|
|
07 FirstName PIC X(10).
|
|
07 MiddleInitial PIC X.
|
|
07 Surname PIC X(15).
|
|
----
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
=== duplicates: S1728
|
|
|
|
=== on 8 Aug 2014, 19:24:07 Ann Campbell wrote:
|
|
rolled into RSPEC-1728
|
|
|
|
|
|
endif::env-github,rspecator-view[]
|