Lars Hvam

TYPES should also trigger https://rules.abaplint.org/fully_type_constants/ ```abap TYPES barfoo(20). DATA foobar(20). ``` and ```abap TYPES: BEGIN OF t_items, mark, END OF t_items, ```

end of selection is a separate event, not the corresponding end statement like FORM ENDFORM ```abap START-OF-SELECTION. PERFORM sdf. COMMIT WORK. END-OF-SELECTION. ```

CREATE OBJECT, check parameters

1

perhaps this is working, but then I'd like it to show the parameters at hover

RETURN as last statement

5

```abap RETURN. ENDIF. ENDMETHOD. ```

```abap CLASS lcx_test DEFINITION INHERITING FROM cx_static_check. PUBLIC SECTION. METHODS sap1_to_sap2_e FOR TESTING RAISING cx_root. ENDCLASS. ```

ending with a dash, ```abap /ui2/cl_json=>deserialize( EXPORTING json = lv_json pretty_name = /ui2/cl_json=>pretty_mode- CHANGING data = stru ). ```

```abap CLASS lcl DEFINITION. PUBLIC SECTION. CLASS-DATA foo TYPE i READ-ONLY. ENDCLASS. CLASS lcl IMPLEMENTATION. ENDCLASS. START-OF-SELECTION. lcl=>foo = 2. ```

only report if there are no static exceptions defined for the method performance relevant and EXPORTING?

takes the default/input configuration file * change the target to 702 * outputs result to a new configuration parameter folder = `downport` * apply quick fixes this will avoid some...