abap-file-formats-tools
abap-file-formats-tools copied to clipboard
enable rule dangerous_statement
trafficstars
I've disabled rule dangerous_statement in the config
suggest refactoring and enabling the rule again
suggest that this code, as such, generate the code to memory, where it can be picked up and written as a file to a git repository, from which the dangerous/import can happen
as a consequence, the code must only contain unit tests, suggest moving integration tests to the layer that uses the application
note: the dangerous statements are in testclasses, which is a no-go IMHO
do integration test outside of the normal tests