ConjuringCoffee

> on the other hand, the existing option "Remove empty line above ENDCLASS" is too unspecific, you'd actually want an empty line if the last section isn't empty, right? Seems...

Let's take another example: ```abap rs_result = VALUE #( comp_1 = VALUE #( some_field = '0a01' something = 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa1' ) comp_2 = VALUE #( example = 'b' very_long_field = 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa2'...

> Maybe keep cases where an empty line is found after the opening command, too? That seems like a good idea to me. 😊

> But in contexts which allow for both (and even _use_ both) tables with and without header lines, it might actually help readability to use `[]` – otherwise, readers would...

So removing the square brackets in the OO context is also out of scope? 😧

> Note that you can still access internal tables with header line inside methods and should be able to clear their contents and header line separately, you just cannot declare...

I support this suggestion. :) By the way, you should prefer `xsdbool` to `boolc`. See here for more details: https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md#use-xsdbool-to-set-boolean-variables You can also watch this issue for a contribution guideline:...

Since last month the ABAP Cleaner has workspace-specific settings. You could have one workspace for S/4 and one for ECC systems. The setting for the ABAP release can then be...

Oh, I didn't know that the ABAP Cleaner automatically detects the system's version... in this case, switching the workspace isn't necessary after all! The UI doesn't make that quite clear...

With regards to the [recent announcements](https://community.sap.com/t5/technology-blog-posts-by-sap/abap-development-tools-for-vs-code-everything-you-need-to-know/ba-p/14258129), are there any plans for a VS Code plugin now? 😉