Domain entities constructor should be private

[codelytv]

Domain entities constructor should be private

[JavierCane]

Hi @Miczeq22!

Good one, thanks for pointing it out 😊

We normally leave the default constructor set as public in order to be able to reconstruct that entity in a specific state without recording any events. That is usually useful for instance while recovering it from the database, or while instantiating it for a specific test case.

It is true that right now we are using the fromPrimitives method in our Mongo repositories and in the Elasticsearch ones, but the ObjectMothers would be still needing that default constructor.

Here we have two alternatives:

• Using the fromPrimitives also in our ObjectMothers in order to be able to set as private the default constructor
• Leave the default constructor as public and assume that the fact that we shouldn't use it from our use cases in order to avoid missing out any domain event recording is a convention not enforced by code.

Taking into account that trade-off, we would opt for the second option. Why:

• We don't want to assume more complexity in each of our ObjectMothers
• We understand that the development team has enough maturity regarding these topics in order to assume that convention

This is a decision that could be reconsidered in a future 🙂