Hi Bryce, Lots of activity this month on things like Zend_Filter_Input and your new proposal, which is good.
So you know our company are using Zend_Validate quite extensively. We're working on an E-Commerce system based on ZF which obviously we're trying to keep up with any changes as they occur. So I certainly advocate change if it's good for the framework. I've only just seen your proposal (http://framework.zend.com/wiki/display/ZFPROP/Zend_Validate_Builder+-+Bryce +Lohr) so will read through it soon, so apologies if this question is answered in there. My initial question is why do you want to allow an empty string to validate? In the context of, say, validating a URL or email address I really wouldn't want an empty string to pass through. If a form says an element is optional, I'd say you need to declare that in your code. I believe a safer default would be to not allow empty strings through. best wishes, Simon > > Hi all, > > > > I've proposed some changes to Zend_Validate_* classes that would > > not be backward compatible. Specifically, I had proposed to change > > the default behavior all the standard validators to consider the > > empty string a valid value. > > > > Now, I've been operating under the assumption that hardly anyone is > > using the current Zend_Validate_* classes, due to the fact that > > it's a hassle to validate a lot of data at once. I figured that if > > few people were actually using these, then the cost of making this > > backward-incompatible change was low. The benefit of the change is > > that it would provide a lot of flexibility in the proposed > > Zend_Validate_Builder class. > > > > I may be way off base with my assumption here, so I'd like to find > > out how many of you are actually using the current Zend_Validate_* > > classes. Obviously, if a lot of people are, in fact, using them, > > then it's not feasible to make this proposed change. > > > > Regards, > > Bryce Lohr
