Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarified Slices documentation #1366

Merged
merged 1 commit into from
Jan 25, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,11 @@
* The top level packages under 'myapp' could be considered slices according to different domain aspects.<br>
* Thus there could be a slice 'Order' housing all the classes from the {@code order} package, a slice 'Customer'
* housing all the classes from the {@code customer} package and so on.
* <p>
* Note that a {@link Slice} does not necessarily represent a subpackage inside some root package.
* The example above is just a common use case, but a {@link Slice} can technically represent any set
* of {@link JavaClass}es.
* </p>
*/
@PublicAPI(usage = ACCESS)
public final class Slice extends ForwardingSet<JavaClass> implements HasDescription, CanOverrideDescription<Slice> {
Expand Down
Loading