have read this post. I can't understand why people so often love to write custom code, making things more complex than they should be. why you are choosing enterprise framework if you love write code ? chose Laravel // chose Phalcon // chose YII2 (or whatever the correct name is). Symfony life-cycle is controlled using Listeners. and when you are working with callback based system, making sure this system won't have invalid data will add majority of complexity. I don't argue that it is useless. but if you don't have complex case, why you need make some strange behavior with ValueObjects ? make setters make getters write clean code and read the code around you. don't need to live with bunch of incapsulated things do that like that. okay we will make saving data to database with Form + Entity + DTO and will add also 5 DTOS for external transfer, just in case some time it will help us.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
have read this post. I can't understand why people so often love to write custom code, making things more complex than they should be. why you are choosing enterprise framework if you love write code ? chose Laravel // chose Phalcon // chose YII2 (or whatever the correct name is). Symfony life-cycle is controlled using Listeners. and when you are working with callback based system, making sure this system won't have invalid data will add majority of complexity. I don't argue that it is useless. but if you don't have complex case, why you need make some strange behavior with ValueObjects ? make setters make getters write clean code and read the code around you. don't need to live with bunch of incapsulated things do that like that. okay we will make saving data to database with Form + Entity + DTO and will add also 5 DTOS for external transfer, just in case some time it will help us.