Is it proper to put the validation (Zend_Filter_Input) inside of a function
called validateAction (for example) inside a controller? To address input
errors I pass the error object from the Zend_Filter_Input into the view. I
read the comments on the Zend_Filter_Input component proposal, and I noticed
the discrepancy between simplicity and proper separation. I like very much
that you are keeping Zend Framework simple, however, I believe that going
the "easy" route can cause problems later. My first few sentences are what I
gathered to be the proper method of checking input, validating, and
outputting text errors. I would like to know if I am correct. I want to keep
everything separated. Things like translation may very well become difficult
if I don't keep the separation. I think the solution I came up with is very
"simple." I also believe it would let you use a different helper depending
on your view, such as HTML or CLI. I have also seen discussions regarding
the model doing the validation. Should the model contain a function that
uses Zend_Validate and returns the resulting object?
--
View this message in context:
http://www.nabble.com/Input-Validation-and-Error-reporting.-tf4692637s16154.html#a13412740
Sent from the Zend Framework mailing list archive at Nabble.com.
