Current Behaviour
Here is the sample source code after applying AbapCleaner,
METHODS my_test_method FOR TESTING RAISING cx_exception_1 cx_exception_2 cx_exception_3 cx_exception_4 cx_exception_5.
Expectation
When we use quick assist(Ctrl+1) for "Add raising declarations", the source code is formatted as below. I think the same must be applied instead of keeping them in a line.
METHODS my_test_method FOR TESTING
RAISING
cx_exception_1
cx_exception_2
cx_exception_3
cx_exception_4
cx_exception_5.
good point, I think we should add options for this, so you could choose
whether or not RAISING and/or the exception class names should continue on the same line (similar to the options in cleanup rule "Align METHODS declarations")
whether or not the exception classes should be listed below each other (similar to the options in cleanup rule "Align CLEAR:, FREE: and SORT")
Current Behaviour Here is the sample source code after applying AbapCleaner,
METHODS my_test_method FOR TESTING RAISING cx_exception_1 cx_exception_2 cx_exception_3 cx_exception_4 cx_exception_5.
Expectation When we use quick assist(Ctrl+1) for "Add raising declarations", the source code is formatted as below. I think the same must be applied instead of keeping them in a line.