Fake package encapsulation

[larshp]

Fake package encapsulation

• Database table to structure or data element
• Data element to domain
• Class to interface
• Code to message class
• etc.

Configuration:

• List of packages
• Checkbox to allow references to SAP standard objects

is it possible to call some standard functionality?

[larshp]

https://github.com/larshp/abapOpenChecks/blob/master/src/checks/zcl_aoc_check_61.clas.abap

[larshp]

SELF_CONTAINED SELF_CONTAINED_ALLOW_STANDARD NO_REFERENCES_IN NO_REFERENCES_OUT

[larshp]

branch https://github.com/larshp/abapOpenChecks/tree/fake

[ConjuringCoffee]

@larshp, I was trying to find out what the purpose of the characteristics ZAOC_ENCAPSULATION, ZAOC_ENCAPSULATION_OBJECTS and ZAOC_ENCAPSULATION_PACKAGES is. It looks like it was in preparation for this check (CHECK_61), right?

Can you please elaborate on the status of the implementation? The documentation only says work in progress and todo.

I have not worked with object characteristics before, which is why I am curious about this. The idea looks interesting, maybe I can support.

[larshp]

the standard package interfaces is a mess IMHO, so this was one take to try to fix it

however, I dont think its relevant anymore, as its easy to enforce and check any set of encapsulation with abaplint

[ConjuringCoffee]

I believe the functionality is still relevant. 😊 A check like this would enable to check encapsulation even if the system isn't fully working with abapGit / abapLint. (Ours certainly isn't yet...)

I'm imagining checks for:

• Is this object used by another object that isn't allowed to?
• Is this object using any objects it isn't allowed to?

[larshp]

well, I choose to spend my time on getting abapGit / abaplint working

I guess characteristics are not released in Steampunk, so its a lost cause anyhow, looking long term