Lars Hvam

yea, I agree, but its strictly not what the description conveys it should be something like "Dont use inline in unrelated branches" or "Only use inline within branch where its...

when there are zero issues found it will return `0` fix the issues by fixing the code, or adjust the configuration to be less strict

below configuration will disable all rules, with all rules disables it returns zero ```json { "global": { "files": "/src/**/*.*", "exclude": [], "noIssues": [], "skipGeneratedGatewayClasses": true, "skipGeneratedPersistentClasses": true, "skipGeneratedFunctionGroups": true, "useApackDependencies":...

Nothing currently built in to change the status based on the number of findings IMHO it goes against the ideas of CI https://www.petrikainulainen.net/programming/unit-testing/why-you-should-keep-your-build-green/ you want to keep the build clean/green,...

thats a different topic and again, if some errors are hidden, how can the developer determine which are issues and which are not? Plus it will never get you to...

the rule does currently not take the synchronized texts into account, suggest disabling the rule for now if you use synchronized texts

by default everything is enabled in abaplint, but some rules might be only valid for specific scenarios, or rules might be conflicting, its up to you to decide what is...

should add it as an option in https://rules.abaplint.org/prefix_is_current_class/ consider all rules like a box of chocolates, enable those that you like, and leave the rest for someone else to enjoy...

so, these are not good, ```abap lo_obj->some_static_method( ). some_static_method( ). ``` and `cl_foobar=>some_static_method( ).` is good

@pokrakam I cannot find the rule mentioned in https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md ?