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
I'm in the "always inline declare and define and declare and define as close as possible to definitions" and not the "declare all variables at the start of any function" crowd.
So it'd be nice to have an option in the rule "Standardize empty lines within methods" rule, that instead of adding an empty line before any executable statement adds an empty line before any statement in a method.
This would maybe require a checkbox so either or option can be chosen.
So this:
METHODget_next_config_id.
DATA lt_sddocs TYPE TABLE OF sales_key.
lt_sddocs =VALUE #( ( vbeln = mv_contract ) ).
DATA lt_cucfg TYPE TABLE OF bapicucfgm.
Doesn't get changed to this:
METHODget_next_config_id.
DATA lt_sddocs TYPE TABLE OF sales_key.
lt_sddocs =VALUE #( ( vbeln = mv_contract ) ).
DATA lt_cucfg TYPE TABLE OF bapicucfgm.
Thanks all for your amazing work.
The text was updated successfully, but these errors were encountered:
This would be indeed an good option. Old legacy programmers prefer the second style. Based on the clean code samples, the first style would be also nice.
I'm in the "always inline declare and define and declare and define as close as possible to definitions" and not the "declare all variables at the start of any function" crowd.
So it'd be nice to have an option in the rule "Standardize empty lines within methods" rule, that instead of adding an empty line before any executable statement adds an empty line before any statement in a method.
This would maybe require a checkbox so either or option can be chosen.
So this:
Doesn't get changed to this:
Thanks all for your amazing work.
The text was updated successfully, but these errors were encountered: