2023-05-03 11:06:20 +02:00
== Why is this an issue?
2021-06-08 14:23:48 +02:00
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.
2023-05-03 11:06:20 +02:00
=== Noncompliant code example
2021-06-08 14:23:48 +02:00
2022-02-04 17:28:24 +01:00
[source,text]
2021-06-08 14:23:48 +02:00
----
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
----
2023-05-03 11:06:20 +02:00
=== Compliant solution
2021-06-08 14:23:48 +02:00
2022-02-04 17:28:24 +01:00
[source,text]
2021-06-08 14:23:48 +02:00
----
01 StudentDetails.
05 StudentId PIC 9(7).
05 StudentName.
07 FirstName PIC X(10).
07 MiddleInitial PIC X.
07 Surname PIC X(15).
----
2022-01-25 18:36:46 +01:00
ifdef::env-github,rspecator-view[]
'''
== Comments And Links
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== duplicates: S1728
=== on 8 Aug 2014, 19:24:07 Ann Campbell wrote:
rolled into RSPEC-1728
2022-01-25 18:36:46 +01:00
endif::env-github,rspecator-view[]