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
{{ message }}
Repository navigation
Error executing rule 'Align SELECT lists': First token 'case' unexpected for a term #229
I've been getting this error for the new cleaning rules added for aligning the SELECT lists (Screenshot Attached). It's just the case statement. If there's any way to rewrite the syntax without getting the error, please share. Else, please check if this issue is fixable.
Also, if we can get a new option added for aligning the joins "below the SELECT clause + 2" instead of/along with "below the table name + 2", just like I did in the screenshot attached, that'd be really awesome!!
Thanks!
thanks a lot for reporting this! That's definitely a bug on ABAP cleaner side (so, no reason to rewrite your code). Will look into it!
I shall also check about the position of the JOINs. However, I'm not sure whether this will easily be possible, because these joins are not considered as an independent clause (such as FROM, WHERE, GROUP BY etc.), but as part of the FROM clause.
Activity
jmgrassau commentedon Jan 17, 2024
Hi Yash,
thanks a lot for reporting this! That's definitely a bug on ABAP cleaner side (so, no reason to rewrite your code). Will look into it!
I shall also check about the position of the JOINs. However, I'm not sure whether this will easily be possible, because these joins are not considered as an independent clause (such as FROM, WHERE, GROUP BY etc.), but as part of the FROM clause.
Kind regards,
Jörg-Michael
jmgrassau commentedon Jan 17, 2024
Hi Yash,
this bug will be fixed with the next release.
Kind regards,
Jörg-Michael
this-yash commentedon Jan 17, 2024
Sure, Thanks!
fix AlignSelectListsRule for FIELDS with one CASE element (SAP#229)
fix AlignSelectListsRule for FIELDS with one CASE element (#229)
jmgrassau commentedon Feb 12, 2024
Hi Yash,
thanks again for this bug report – this bug should now be fixed with version 1.13.1, which was just released!
Kind regards,
Jörg-Michael