@abaplint/core 2.113.85 → 2.113.87

package/build/src/rules/exit_or_check.js

@@ -24,10 +24,10 @@ class ExitOrCheck extends _abap_rule_1.ABAPRule {
         return {
             key: "exit_or_check",
             title: "Find EXIT or CHECK outside loops",
-            shortDescription: `Detects usages of EXIT or CHECK statements outside of loops.
+            shortDescription: `Detects usages of EXIT or CHECK statements outside of loops.
 Use RETURN to leave procesing blocks instead.`,
-            extendedInformation: `https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-US/abenleave_processing_blocks.htm
-https://help.sap.com/doc/abapdocu_750_index_htm/7.50/en-US/abapcheck_processing_blocks.htm
+            extendedInformation: `https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-US/abenleave_processing_blocks.htm
+https://help.sap.com/doc/abapdocu_750_index_htm/7.50/en-US/abapcheck_processing_blocks.htm
 https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#check-vs-return`,
             tags: [_irule_1.RuleTag.Styleguide, _irule_1.RuleTag.SingleFile, _irule_1.RuleTag.Quickfix],
         };

package/build/src/rules/expand_macros.js

@@ -21,12 +21,12 @@ class ExpandMacros extends _abap_rule_1.ABAPRule {
             key: "expand_macros",
             title: "Expand Macros",
             shortDescription: `Allows expanding macro calls with quick fixes`,
-            extendedInformation: `Macros: https://help.sap.com/doc/abapdocu_752_index_htm/7.52/en-US/abenmacros_guidl.htm
-
+            extendedInformation: `Macros: https://help.sap.com/doc/abapdocu_752_index_htm/7.52/en-US/abenmacros_guidl.htm
+
 Note that macros/DEFINE cannot be used in the ABAP Cloud programming model`,
-            badExample: `DEFINE _hello.
-  WRITE 'hello'.
-END-OF-DEFINITION.
+            badExample: `DEFINE _hello.
+  WRITE 'hello'.
+END-OF-DEFINITION.
 _hello.`,
             goodExample: `WRITE 'hello'.`,
             tags: [_irule_1.RuleTag.Styleguide, _irule_1.RuleTag.Quickfix, _irule_1.RuleTag.Upport],

package/build/src/rules/exporting.js

@@ -22,7 +22,7 @@ class Exporting extends _abap_rule_1.ABAPRule {
             shortDescription: `Detects EXPORTING statements which can be omitted.`,
             badExample: `call_method( EXPORTING foo = bar ).`,
             goodExample: `call_method( foo = bar ).`,
-            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#omit-the-optional-keyword-exporting
+            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#omit-the-optional-keyword-exporting
 https://docs.abapopenchecks.org/checks/30/`,
             tags: [_irule_1.RuleTag.Styleguide, _irule_1.RuleTag.Quickfix, _irule_1.RuleTag.SingleFile],
         };

package/build/src/rules/forbidden_identifier.js

@@ -26,7 +26,7 @@ class ForbiddenIdentifier extends _abap_rule_1.ABAPRule {
             key: "forbidden_identifier",
             title: "Forbidden Identifier",
             shortDescription: `Forbid use of specified identifiers, list of regex.`,
-            extendedInformation: `Used in the transpiler to find javascript keywords in ABAP identifiers,
+            extendedInformation: `Used in the transpiler to find javascript keywords in ABAP identifiers,
 https://github.com/abaplint/transpiler/blob/bda94b8b56e2b7f2f87be2168f12361aa530220e/packages/transpiler/src/validation.ts#L44`,
             tags: [_irule_1.RuleTag.SingleFile],
         };

package/build/src/rules/forbidden_void_type.js

@@ -28,8 +28,8 @@ class ForbiddenVoidType {
             key: "forbidden_void_type",
             title: "Forbidden Void Types",
             shortDescription: `Avoid usage of specified void types.`,
-            extendedInformation: `Inspiration:
-BOOLEAN, BOOLE_D, CHAR01, CHAR1, CHAR10, CHAR12, CHAR128, CHAR2, CHAR20, CHAR4, CHAR70,
+            extendedInformation: `Inspiration:
+BOOLEAN, BOOLE_D, CHAR01, CHAR1, CHAR10, CHAR12, CHAR128, CHAR2, CHAR20, CHAR4, CHAR70,
 DATS, TIMS, DATUM, FLAG, INT4, NUMC3, NUMC4, SAP_BOOL, TEXT25, TEXT80, X255, XFELD`,
         };
     }

package/build/src/rules/fully_type_itabs.js

@@ -20,9 +20,9 @@ class FullyTypeITabs extends _abap_rule_1.ABAPRule {
             key: "fully_type_itabs",
             title: "Fully type internal tables",
             shortDescription: `No implict table types or table keys`,
-            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#use-the-right-table-type
+            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#use-the-right-table-type
 https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#avoid-default-key`,
-            badExample: `DATA lt_foo TYPE TABLE OF ty.
+            badExample: `DATA lt_foo TYPE TABLE OF ty.
 DATA lt_bar TYPE STANDARD TABLE OF ty.`,
             goodExample: `DATA lt_foo TYPE STANDARD TABLE OF ty WITH EMPTY KEY.`,
             tags: [_irule_1.RuleTag.SingleFile],

package/build/src/rules/functional_writing.js

@@ -28,26 +28,26 @@ class FunctionalWriting extends _abap_rule_1.ABAPRule {
             key: "functional_writing",
             title: "Use functional writing",
             shortDescription: `Detects usage of call method when functional style calls can be used.`,
-            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#prefer-functional-to-procedural-calls
+            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#prefer-functional-to-procedural-calls
 https://docs.abapopenchecks.org/checks/07/`,
             tags: [_irule_1.RuleTag.Styleguide, _irule_1.RuleTag.Quickfix, _irule_1.RuleTag.SingleFile],
-            badExample: `CALL METHOD zcl_class=>method( ).
-CALL METHOD cl_abap_typedescr=>describe_by_name
-  EXPORTING
-    p_name         = 'NAME'
-  RECEIVING
-    p_descr_ref    = lr_typedescr
-  EXCEPTIONS
-    type_not_found = 1
+            badExample: `CALL METHOD zcl_class=>method( ).
+CALL METHOD cl_abap_typedescr=>describe_by_name
+  EXPORTING
+    p_name         = 'NAME'
+  RECEIVING
+    p_descr_ref    = lr_typedescr
+  EXCEPTIONS
+    type_not_found = 1
     OTHERS         = 2.`,
-            goodExample: `zcl_class=>method( ).
-cl_abap_typedescr=>describe_by_name(
-  EXPORTING
-    p_name         = 'NAME'
-  RECEIVING
-    p_descr_ref    = lr_typedescr
-  EXCEPTIONS
-    type_not_found = 1
+            goodExample: `zcl_class=>method( ).
+cl_abap_typedescr=>describe_by_name(
+  EXPORTING
+    p_name         = 'NAME'
+  RECEIVING
+    p_descr_ref    = lr_typedescr
+  EXCEPTIONS
+    type_not_found = 1
     OTHERS         = 2 ).`,
         };
     }

package/build/src/rules/global_class.js

@@ -19,14 +19,14 @@ class GlobalClass extends _abap_rule_1.ABAPRule {
             key: "global_class",
             title: "Global class checks",
             shortDescription: `Checks related to global classes`,
-            extendedInformation: `* global classes must be in own files
-
-* file names must match class name
-
-* file names must match interface name
-
-* global classes must be global definitions
-
+            extendedInformation: `* global classes must be in own files
+
+* file names must match class name
+
+* file names must match interface name
+
+* global classes must be global definitions
+
 * global interfaces must be global definitions`,
             tags: [_irule_1.RuleTag.Syntax],
         };

package/build/src/rules/identical_conditions.js

@@ -33,21 +33,21 @@ class IdenticalConditions extends _abap_rule_1.ABAPRule {
         return {
             key: "identical_conditions",
             title: "Identical conditions",
-            shortDescription: `Find identical conditions in IF + CASE + WHILE etc
-
+            shortDescription: `Find identical conditions in IF + CASE + WHILE etc
+
 Prerequsites: code is pretty printed with identical cAsE`,
             tags: [_irule_1.RuleTag.SingleFile],
-            badExample: `IF foo = bar OR 1 = a OR foo = bar.
-ENDIF.
-CASE bar.
-  WHEN '1'.
-  WHEN 'A' OR '1'.
+            badExample: `IF foo = bar OR 1 = a OR foo = bar.
+ENDIF.
+CASE bar.
+  WHEN '1'.
+  WHEN 'A' OR '1'.
 ENDCASE.`,
-            goodExample: `IF foo = bar OR 1 = a.
-ENDIF.
-CASE bar.
-  WHEN '1'.
-  WHEN 'A'.
+            goodExample: `IF foo = bar OR 1 = a.
+ENDIF.
+CASE bar.
+  WHEN '1'.
+  WHEN 'A'.
 ENDCASE.`,
         };
     }

package/build/src/rules/identical_contents.js

@@ -21,23 +21,23 @@ class IdenticalContents extends _abap_rule_1.ABAPRule {
             key: "identical_contents",
             title: "Identical contents",
             shortDescription: `Find identical contents in blocks inside IFs, both in the beginning and in the end.`,
-            extendedInformation: `
-Prerequsites: code is pretty printed with identical cAsE
-
+            extendedInformation: `
+Prerequsites: code is pretty printed with identical cAsE
+
 Chained statments are ignored`,
             tags: [_irule_1.RuleTag.SingleFile],
-            badExample: `IF foo = bar.
-  WRITE 'bar'.
-  WRITE 'world'.
-ELSE.
-  WRITE 'foo'.
-  WRITE 'world'.
+            badExample: `IF foo = bar.
+  WRITE 'bar'.
+  WRITE 'world'.
+ELSE.
+  WRITE 'foo'.
+  WRITE 'world'.
 ENDIF.`,
-            goodExample: `IF foo = bar.
-  WRITE 'bar'.
-ELSE.
-  WRITE 'foo'.
-ENDIF.
+            goodExample: `IF foo = bar.
+  WRITE 'bar'.
+ELSE.
+  WRITE 'foo'.
+ENDIF.
 WRITE 'world'.`,
         };
     }

package/build/src/rules/identical_descriptions.js

@@ -16,12 +16,12 @@ class IdenticalDescriptions {
             key: "identical_descriptions",
             title: "Identical descriptions",
             shortDescription: `Searches for objects with the same type and same description`,
-            extendedInformation: `Case insensitive
-
-Only checks the master language descriptions
-
-Dependencies are skipped
-
+            extendedInformation: `Case insensitive
+
+Only checks the master language descriptions
+
+Dependencies are skipped
+
 Works for: INTF, CLAS, DOMA, DTEL, FUNC in same FUGR`,
             tags: [],
         };

package/build/src/rules/if_in_if.js

@@ -21,43 +21,43 @@ class IfInIf extends _abap_rule_1.ABAPRule {
             key: "if_in_if",
             title: "IF in IF",
             shortDescription: `Detects nested ifs which can be refactored.`,
-            extendedInformation: `
-Directly nested IFs without ELSE can be refactored to a single condition using AND.
-
-ELSE condtions with directly nested IF refactored to ELSEIF, quickfixes are suggested for this case.
-
-https://docs.abapopenchecks.org/checks/01/
+            extendedInformation: `
+Directly nested IFs without ELSE can be refactored to a single condition using AND.
+
+ELSE condtions with directly nested IF refactored to ELSEIF, quickfixes are suggested for this case.
+
+https://docs.abapopenchecks.org/checks/01/
 https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#keep-the-nesting-depth-low`,
-            badExample: `IF condition1.
-  IF condition2.
-    ...
-  ENDIF.
-ENDIF.
-
-IF condition1.
-  ...
-ELSE.
-  IF condition2.
-    ...
-  ENDIF.
+            badExample: `IF condition1.
+  IF condition2.
+    ...
+  ENDIF.
+ENDIF.
+
+IF condition1.
+  ...
+ELSE.
+  IF condition2.
+    ...
+  ENDIF.
 ENDIF.`,
-            goodExample: `IF ( condition1 ) AND ( condition2 ).
-  ...
-ENDIF.
-
-IF condition1.
-  ...
-ELSEIF condition2.
-  ...
-ENDIF.
-
-CASE variable.
-  WHEN value1.
-  ...
-  WHEN value2.
-    IF condition2.
-      ...
-    ENDIF.
+            goodExample: `IF ( condition1 ) AND ( condition2 ).
+  ...
+ENDIF.
+
+IF condition1.
+  ...
+ELSEIF condition2.
+  ...
+ENDIF.
+
+CASE variable.
+  WHEN value1.
+  ...
+  WHEN value2.
+    IF condition2.
+      ...
+    ENDIF.
 ENDCASE.`,
             tags: [_irule_1.RuleTag.Styleguide, _irule_1.RuleTag.SingleFile, _irule_1.RuleTag.Quickfix],
         };

package/build/src/rules/implement_methods.js

@@ -102,9 +102,9 @@ class ImplementMethods extends _abap_rule_1.ABAPRule {
         for (const i of ((_a = file.getStructure()) === null || _a === void 0 ? void 0 : _a.findAllStatements(Statements.ClassImplementation)) || []) {
             const name = (_b = i.findFirstExpression(Expressions.ClassName)) === null || _b === void 0 ? void 0 : _b.getFirstToken().getStr().toUpperCase();
             if (name === impl.identifier.getName().toUpperCase()) {
-                return edit_helper_1.EditHelper.insertAt(file, i.getLastToken().getEnd(), `
-  METHOD ${methodName.toLowerCase()}.
-    RETURN. " todo, implement method
+                return edit_helper_1.EditHelper.insertAt(file, i.getLastToken().getEnd(), `
+  METHOD ${methodName.toLowerCase()}.
+    RETURN. " todo, implement method
   ENDMETHOD.`);
             }
         }

package/build/src/rules/implicit_start_of_selection.js

@@ -22,14 +22,14 @@ class ImplicitStartOfSelection extends _abap_rule_1.ABAPRule {
             key: "implicit_start_of_selection",
             title: "Implicit START-OF-SELECTION",
             shortDescription: `Add explicit selection screen event handling`,
-            extendedInformation: `Only runs for executable programs
-
+            extendedInformation: `Only runs for executable programs
+
 https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-us/abapstart-of-selection.htm`,
             tags: [_irule_1.RuleTag.SingleFile],
-            badExample: `REPORT zfoo.
+            badExample: `REPORT zfoo.
 WRITE 'hello'.`,
-            goodExample: `
-START-OF-SELECTION.
+            goodExample: `
+START-OF-SELECTION.
   WRITE 'hello'.`,
         };
     }

package/build/src/rules/in_statement_indentation.js

@@ -31,19 +31,19 @@ class InStatementIndentation extends _abap_rule_1.ABAPRule {
             key: "in_statement_indentation",
             title: "In-statement indentation",
             shortDescription: "Checks alignment within statements which span multiple lines.",
-            extendedInformation: `Lines following the first line should be indented once (2 spaces).
-
-For block declaration statements, lines after the first should be indented an additional time (default: +2 spaces)
+            extendedInformation: `Lines following the first line should be indented once (2 spaces).
+
+For block declaration statements, lines after the first should be indented an additional time (default: +2 spaces)
 to distinguish them better from code within the block.`,
-            badExample: `IF 1 = 1
-  AND 2 = 2.
-  WRITE 'hello' &&
-  'world'.
+            badExample: `IF 1 = 1
+  AND 2 = 2.
+  WRITE 'hello' &&
+  'world'.
 ENDIF.`,
-            goodExample: `IF 1 = 1
-    AND 2 = 2.
-  WRITE 'hello' &&
-    'world'.
+            goodExample: `IF 1 = 1
+    AND 2 = 2.
+  WRITE 'hello' &&
+    'world'.
 ENDIF.`,
             tags: [_irule_1.RuleTag.Whitespace, _irule_1.RuleTag.Quickfix, _irule_1.RuleTag.SingleFile],
         };

package/build/src/rules/indentation.js

@@ -40,23 +40,23 @@ class Indentation extends _abap_rule_1.ABAPRule {
             title: "Indentation",
             shortDescription: `Checks indentation`,
             tags: [_irule_1.RuleTag.Whitespace, _irule_1.RuleTag.Quickfix, _irule_1.RuleTag.SingleFile],
-            badExample: `CLASS lcl DEFINITION.
-PRIVATE SECTION.
-METHODS constructor.
-ENDCLASS.
-
-CLASS lcl IMPLEMENTATION.
-METHOD constructor.
-ENDMETHOD.
+            badExample: `CLASS lcl DEFINITION.
+PRIVATE SECTION.
+METHODS constructor.
+ENDCLASS.
+
+CLASS lcl IMPLEMENTATION.
+METHOD constructor.
+ENDMETHOD.
 ENDCLASS.`,
-            goodExample: `CLASS lcl DEFINITION.
-  PRIVATE SECTION.
-    METHODS constructor.
-ENDCLASS.
-
-CLASS lcl IMPLEMENTATION.
-  METHOD constructor.
-  ENDMETHOD.
+            goodExample: `CLASS lcl DEFINITION.
+  PRIVATE SECTION.
+    METHODS constructor.
+ENDCLASS.
+
+CLASS lcl IMPLEMENTATION.
+  METHOD constructor.
+  ENDMETHOD.
 ENDCLASS.`,
         };
     }

package/build/src/rules/intf_referencing_clas.js

@@ -26,9 +26,9 @@ class IntfReferencingClas {
             key: "intf_referencing_clas",
             title: "INTF referencing CLAS",
             shortDescription: `Interface contains references to class`,
-            extendedInformation: `Only global interfaces are checked.
-      Only first level references are checked.
-      Exception class references are ignored.
+            extendedInformation: `Only global interfaces are checked.
+      Only first level references are checked.
+      Exception class references are ignored.
       Void references are ignored.`,
         };
     }

package/build/src/rules/invalid_table_index.js

@@ -22,9 +22,9 @@ class InvalidTableIndex extends _abap_rule_1.ABAPRule {
             title: "Invalid Table Index",
             shortDescription: `Issues error for constant table index zero, as ABAP starts from 1`,
             tags: [_irule_1.RuleTag.SingleFile, _irule_1.RuleTag.Quickfix],
-            badExample: `DATA(first) = table[ 0 ].
+            badExample: `DATA(first) = table[ 0 ].
 READ TABLE gt_stack ASSIGNING <ls_stack> INDEX 0.`,
-            goodExample: `DATA(first) = table[ 1 ].
+            goodExample: `DATA(first) = table[ 1 ].
 READ TABLE gt_stack ASSIGNING <ls_stack> INDEX 1.`,
         };
     }

package/build/src/rules/line_break_style.js

@@ -15,8 +15,8 @@ class LineBreakStyle {
         return {
             key: "line_break_style",
             title: "Makes sure line breaks are consistent in the ABAP code",
-            shortDescription: `Enforces LF as newlines in ABAP files
-
+            shortDescription: `Enforces LF as newlines in ABAP files
+
 abapGit does not work with CRLF`,
             tags: [_irule_1.RuleTag.Whitespace, _irule_1.RuleTag.SingleFile],
         };

package/build/src/rules/line_length.js

@@ -23,7 +23,7 @@ class LineLength extends _abap_rule_1.ABAPRule {
             key: "line_length",
             title: "Line length",
             shortDescription: `Detects lines exceeding the provided maximum length.`,
-            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#stick-to-a-reasonable-line-length
+            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#stick-to-a-reasonable-line-length
 https://docs.abapopenchecks.org/checks/04/`,
             tags: [_irule_1.RuleTag.Styleguide, _irule_1.RuleTag.SingleFile],
         };

package/build/src/rules/line_only_punc.js

@@ -27,7 +27,7 @@ class LineOnlyPunc extends _abap_rule_1.ABAPRule {
             key: "line_only_punc",
             title: "Line containing only punctuation",
             shortDescription: `Detects lines containing only punctuation.`,
-            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#close-brackets-at-line-end
+            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#close-brackets-at-line-end
 https://docs.abapopenchecks.org/checks/16/`,
             tags: [_irule_1.RuleTag.Styleguide, _irule_1.RuleTag.Quickfix, _irule_1.RuleTag.SingleFile],
             badExample: "zcl_class=>method(\n).",

package/build/src/rules/local_variable_names.js

@@ -30,15 +30,15 @@ class LocalVariableNames extends _abap_rule_1.ABAPRule {
         return {
             key: "local_variable_names",
             title: "Local variable naming conventions",
-            shortDescription: `
-Allows you to enforce a pattern, such as a prefix, for local variables, constants and field symbols.
+            shortDescription: `
+Allows you to enforce a pattern, such as a prefix, for local variables, constants and field symbols.
 Regexes are case-insensitive.`,
             tags: [_irule_1.RuleTag.Naming, _irule_1.RuleTag.SingleFile],
-            badExample: `FORM bar.
-  DATA foo.
+            badExample: `FORM bar.
+  DATA foo.
 ENDFORM.`,
-            goodExample: `FORM bar.
-  DATA lv_foo.
+            goodExample: `FORM bar.
+  DATA lv_foo.
 ENDFORM.`,
         };
     }

package/build/src/rules/macro_naming.js

@@ -28,9 +28,9 @@ class MacroNaming extends _abap_rule_1.ABAPRule {
             shortDescription: `Allows you to enforce a pattern for macro definitions`,
             extendedInformation: `Use rule "avoid_use" to avoid macros altogether.`,
             tags: [_irule_1.RuleTag.Naming, _irule_1.RuleTag.SingleFile],
-            badExample: `DEFINE something.
+            badExample: `DEFINE something.
 END-OF-DEFINITION.`,
-            goodExample: `DEFINE _something.
+            goodExample: `DEFINE _something.
 END-OF-DEFINITION.`,
         };
     }

package/build/src/rules/main_file_contents.js

@@ -22,10 +22,10 @@ class MainFileContents {
             key: "main_file_contents",
             title: "Main file contents",
             shortDescription: `Checks related to report declarations.`,
-            extendedInformation: `Does not run if the target version is Cloud
-
-* PROGs must begin with "REPORT <name>." or "PROGRAM <name>.
-* TYPEs must begin with "TYPE-POOL <name>."
+            extendedInformation: `Does not run if the target version is Cloud
+
+* PROGs must begin with "REPORT <name>." or "PROGRAM <name>.
+* TYPEs must begin with "TYPE-POOL <name>."
 `,
         };
     }

package/build/src/rules/many_parentheses.js

@@ -23,17 +23,17 @@ class ManyParentheses extends _abap_rule_1.ABAPRule {
             title: "Too many parentheses",
             shortDescription: `Searches for expressions where extra parentheses can safely be removed`,
             tags: [_irule_1.RuleTag.SingleFile, _irule_1.RuleTag.Quickfix],
-            badExample: `
-IF ( destination IS INITIAL ).
-ENDIF.
-IF foo = boo AND ( bar = lar AND moo = loo ).
-ENDIF.
+            badExample: `
+IF ( destination IS INITIAL ).
+ENDIF.
+IF foo = boo AND ( bar = lar AND moo = loo ).
+ENDIF.
 `,
-            goodExample: `
-IF destination IS INITIAL.
-ENDIF.
-IF foo = boo AND bar = lar AND moo = loo.
-ENDIF.
+            goodExample: `
+IF destination IS INITIAL.
+ENDIF.
+IF foo = boo AND bar = lar AND moo = loo.
+ENDIF.
 `,
         };
     }

package/build/src/rules/max_one_method_parameter_per_line.js

@@ -21,14 +21,14 @@ class MaxOneMethodParameterPerLine extends _abap_rule_1.ABAPRule {
             title: "Max one method parameter definition per line",
             shortDescription: `Keep max one method parameter description per line`,
             tags: [_irule_1.RuleTag.SingleFile, _irule_1.RuleTag.Whitespace],
-            badExample: `
-METHODS apps_scope_token
-  IMPORTING
+            badExample: `
+METHODS apps_scope_token
+  IMPORTING
     body TYPE bodyapps_scope_token client_id TYPE str.`,
-            goodExample: `
-METHODS apps_scope_token
-  IMPORTING
-    body      TYPE bodyapps_scope_token
+            goodExample: `
+METHODS apps_scope_token
+  IMPORTING
+    body      TYPE bodyapps_scope_token
     client_id TYPE str.`,
         };
     }

package/build/src/rules/max_one_statement.js

@@ -21,11 +21,11 @@ class MaxOneStatement extends _abap_rule_1.ABAPRule {
             key: "max_one_statement",
             title: "Max one statement per line",
             shortDescription: `Checks that each line contains only a single statement.`,
-            extendedInformation: `Does not report empty statements, use rule empty_statement for detecting empty statements.
-
-Does not report anything for chained statements.
-
-https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#no-more-than-one-statement-per-line
+            extendedInformation: `Does not report empty statements, use rule empty_statement for detecting empty statements.
+
+Does not report anything for chained statements.
+
+https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#no-more-than-one-statement-per-line
 https://docs.abapopenchecks.org/checks/11/`,
             tags: [_irule_1.RuleTag.Styleguide, _irule_1.RuleTag.Quickfix, _irule_1.RuleTag.SingleFile],
             badExample: `WRITE foo. WRITE bar.`,

package/build/src/rules/method_length.js

@@ -35,8 +35,8 @@ class MethodLength {
             key: "method_length",
             title: "Method/Form Length",
             shortDescription: `Checks relating to method/form length.`,
-            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#keep-methods-small
-
+            extendedInformation: `https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#keep-methods-small
+
 Abstract methods without statements are considered okay.`,
             tags: [_irule_1.RuleTag.Styleguide, _irule_1.RuleTag.SingleFile],
         };