Timeline for How does accumulating large amounts of business logic on the model objects make building strong service contracts harder?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2014 at 9:32 | comment | added | Neil | Fine, close enough. Edit your answer and I'll vote it up. | |
| Feb 14, 2014 at 9:11 | comment | added | gbjbaanb | Its ok, if its used sparingly - but if you overdo it and put all you validation code there, ytou see it becomes a right old mess of tightly coupled business logic mixed in the presentation layer; just like if you mix all your business logic in the data layer. | |
| Feb 14, 2014 at 8:49 | comment | added | Neil | I agree with this sentiment, but before you can use this analogy, you also have to demonstrate why this is bad. Is all I take from this only that you shouldn't do it because it is in the "wrong place" for a clean architecture? | |
| Feb 14, 2014 at 8:42 | comment | added | gbjbaanb | @Neil - in that many times validation is something that should go in the middle tier too (to be clean) but too often its easier and faster for the user to put the validation code (and the validating data) in the presentation tier too. Its an example of logic being in the wrong place for a clean architecture. | |
| Feb 14, 2014 at 8:39 | comment | added | Neil | I don't think you've properly demonstrated how the question "Should do you do validation in the presentation layer?" is similar to the question asked by the op. If you clarify, I'll vote it up. | |
| Feb 14, 2014 at 8:35 | history | answered | gbjbaanb | CC BY-SA 3.0 |