Scoped access specifier

image

Is it intended that making ModuleA scoped to ModuleB allows ModuleB to access everything marked <internal> in ModuleA?
Shouldn’t only <public> members of ModuleA be accessible instead?

In the provided image, everything marked <internal> inside Data and Inventory modules behaves as if it was <public> to Persistence module. This effect propagates to classes and their <internal> members as well.

No, that’s not intended. Thanks for the report.