Validation logic in Setter methods vs Validation classes/objects

[Jeff_Mott]

Similar discussion:

Are getters and setters bad for domain object model?

Yup, I think ahundiak is on the right track. Traditionally in OO, a class is responsible for keeping its private data in a valid state. If it was possible for a Post object to have a published date but not be in a published state, then that would be invalid. But there’s a trade-off. We would end up using exceptions for simple validation. For example: class User { // ... public function setEmail($email) { // Ensure this object is always valid if (!filter_var($em…

Are getters and setters bad for domain object model?

Yup, I think ahundiak is on the right track. Traditionally in OO, a class is responsible for keeping its private data in a valid state. If it was possible for a Post object to have a published date but not be in a published state, then that would be invalid. But there’s a trade-off. We would end up using exceptions for simple validation. For example: class User { // ... public function setEmail($email) { // Ensure this object is always valid if (!filter_var($em…