Why is package separation missing?

[Marat-Tim]

I remember the project used to have a well-structured package layout
Now all classes are in a single package - why is that?
Is it really just for the sake of encapsulation?

[Marat-Tim]

@yegor256 Looks like you’re the one who committed the change moving all classes into the main package - could you share the reasoning behind that?

[yegor256]

@Marat-Tim that's for the sake of reducing the public surface of the package: https://www.javadoc.io/doc/org.eolang/lints/latest/org/eolang/lints/package-summary.html Now, it's pretty small, just like we want it to be. With packages it will be much larger, confusing our clients.

[Marat-Tim]

@yegor256 But won’t it be inconvenient for us to work without proper package separation?
For example, adding all the new classes related to automatic fixes into org.eolang.lints looks messy
In that case, would it make sense to create a separate package specifically for those classes?

[yegor256]

@Marat-Tim I suggest we stay in one package for now. We have class-name prefixes, to help us group files. A package is something we deliver to a client.

[h1alexbel]

@Marat-Tim still an issue?