2 ms·
You can get reductionist and say there's no reason to do anything. The fact is, most of the time when people have models that represent things, there are going
by mgkimsal 15y ago
You can get reductionist and say there's no reason to do anything. The fact is, most of the time when people have models that represent things, there are going to be basic validation rules to represent standard constraints ("email has to be valid", "fields x/y/z can't be null", etc). Those constraints are specific to the concept of the model itself, outside of any relations it may have, or uses it may have in the rest of the app. To me, that's reason enough to provide for a validation system in a model in framework.
Hell - why have models? There's no reason to tie a model in to a framework - just be flexible and do it however you want, right?