You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could BREAK-POINT statement be considered the same way as local declarations at the beginning of the method so that CHECK in the following code is NOT converted to IF ... RETURN ... ENDIF?
METHOD process.
DATA a TYPE c LENGTH 1.
BREAK-POINT ID fins_rev_rec_acdocp.
CHECK a IS INITIAL.
ENDMETHOD.
The text was updated successfully, but these errors were encountered:
that's a good point, thanks for bringing this up! And I think this is valid for all Checkpoints (ASSERT, BREAK-POINT, LOG-POINT). However, rather than considering them like local declarations, I think it would be better to add an option like "[X] Keep CHECK statement independent of previous ASSERT, BREAK-POINT, or LOG-POINT".
Kind regards,
Jörg-Michael
jmgrassau
added a commit
to jmgrassau/abap-cleaner
that referenced
this issue
Oct 10, 2023
Could BREAK-POINT statement be considered the same way as local declarations at the beginning of the method so that CHECK in the following code is NOT converted to IF ... RETURN ... ENDIF?
The text was updated successfully, but these errors were encountered: