Doctrine without setters

php doctrine-orm domain-driven-design

You will come across many drawbacks, like:

ID is available after persist => solution: using object ids or UUID in entity constructor
- for more see: https://carlosbuenosvinos.com/doctrine-25-ddd-entities-and-identities/
Symfony forms like to use setters => solution: use constructor (as you do) and CQRS
- for more see:
  - http://verraes.net/2013/04/decoupling-symfony2-forms-from-entities/
  - https://webmozart.io/blog/2015/09/09/value-objects-in-symfony-forms/
value objects (like Email object that validates email in it's constructor) => solution: use embeddables
- for more see: https://www.doctrine-project.org/projects/doctrine-orm/en/latest/tutorials/embeddables.html

CodeHunter