Specific indentations

arguable, just an opinion

case 1, try-catch. catch should not be indented

    try.
      call_a_method( ).
    catch cx_static_check into lx. " <<<<<
      process_error( lx ).
    endtry.

case 2, indentation right after class definition/implementation when created with se80 2nd level code is not indented. no problem to indent the definition. But indenting the implementation will add starting spaces when editing a specific method - which looks ugly imho.

class ZCL_MY_CLASS definition
  public
  final
  create private .

public section. " <<<<<
  ...
class ZCL_MY_CLASS implementation.
method CONSTRUCTOR. " <<<<<
  data ...

I know the above is the matter of taste of course. Could it be a good idea to add some params to indentation rule to exclude specific cases like above? (one by one of course). E.g:

    "indentation":{  
      "enabled": true,
      "try-catch-indent": false,
      "class-def-indent": false,
    }

[sbcgua]

if you hint where to look and an examples, i can try to PR if you don’t mind 😃

pretty printer: yes, almost never 😃 Why? Mmmm: don’t know … historically so, maybe I don’t trust them as they sometimes ruin non-standartly formatted but well readable parts of code … 😃

[sbcgua]

Hi @DHEWC001, public section kind of belong to class so it should be

class lcl_class definition.
  public section. <<< indent it too !
    methods xxx.
    data yyyy type i.
endclass.

However in the context of this particular issue you can also specify globalClassSkipFirst = true in indentation rule of the abaplint.json to suppress particulary first class line indentation.

class ZCL_MY_CLASS implementation.
method CONSTRUCTOR. " <<<<<
  data ...