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.

Sign up for GitHub

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

Jump to bottom

Encourage making descendants of Aggregate and AggregatePart final #67

Open
alexander-yevsyukov opened this issue Jan 25, 2017 · 1 comment
Open

Encourage making descendants of Aggregate and AggregatePart final #67

alexander-yevsyukov opened this issue Jan 25, 2017 · 1 comment
Labels
enhancement New feature or request

Comments

@alexander-yevsyukov
Copy link
Contributor

There cannot be such a thing as aggregate inheritance because there can be only one class that handles a type of a command. Therefore we need to encourage users to mark classes they create as final.

A Model Compiler can analyze Java code and issue warnings when classes derived from Aggregate or AggregatePart are not declared as final.
@alexander-yevsyukov alexander-yevsyukov added the enhancement New feature or request label Jan 25, 2017
@alexander-yevsyukov alexander-yevsyukov changed the title Encourage making Aggregate and AggregatePart classes final Encourage making descendants of Aggregate and AggregatePart final Jan 25, 2017
@alexander-yevsyukov
Copy link
Contributor Author

This may prevent spying on such classes in tests.

@alexander-yevsyukov alexander-yevsyukov transferred this issue from SpineEventEngine/core-java Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexander-yevsyukov