Kotlin to support package protected visibility

Language Design
34

Hi, I created account only to comment and say: You are wrong. Guys who developed JAVA language has great Idea to make package scope as a default scope (without keyword). Some devs has hard time to understand of true potential of Package scope and even if I explain to You you will probably not get it. But I will try :smiley: I have one small application with rules:

  1. app has 3 modules/packages: user management, product management, shop
  2. user module does not see any class of product module because it doesn’t need to.
  3. product module does not see any interiors of user module because doesn’t need to.
  4. shop module use published iterfaces/facades (public class (only one per module and dtos) ) of user and product module and do not see their interiors because it doesn’t need to.

the whole code is encapsulated on each package levels.

If my junior dev colleague will change something in product module/package I’m sure that he will not break whole application and what’s more important I have better control of dependencies between modules.

It’s architected that way because each module can be moved to micro-services in future or moved “somewhere” (we do not know that yet) and it is easy because they all has only one point of access for each module (even Controller class is package scope).

Using “internal” I would have to create always 2 modules for dto’s and for service for each module/package
and there would be additional configuration on my head.

It would be great assets to developers if it would be default scope.

There is great presentation of this and package scope: JDD 2017: Keep IT clean: mid-sized building blocks and hexagonal architecture (Jakub Nabrdalik) - YouTube

5 Likes