Hi, On Tue, Sep 12, 2017 at 6:39 AM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote:
> Hi, > > On Tue, Sep 12, 2017 at 6:35 AM, li...@rhsoft.net <li...@rhsoft.net> > wrote: > >> >> Am 11.09.2017 um 23:07 schrieb Yasuo Ohgaki >> >>> On Tue, Sep 12, 2017 at 12:22 AM, Stephen Reay <php-li...@koalephant.com >>> > >>> >>>> So, you still didn’t actually provide an example. I *guess* you’re >>>> talking >>>> about character class validation or something else equally “simple”, >>>> because I can’t imagine what else would be a common enough case that >>>> you’d >>>> want to have built-in rules for, and that you wouldn’t internally use >>>> RegExp to test anyway. >>>> >>> >>> Your request is like "Devil's Proof". Example code that cannot do things >>> with existing API cannot exist with meaningful manner. It can be >>> explained >>> why it cannot, though. Try what "validate" string validator can do, >>> Then you'll see. >>> >>> There is no STRING validation filter currently. This fact alone, >>> it could be said "filter cannot do string validation currently". >>> >>> List of problems in current validation filter >>> >> but you still fail to explain why in the world you don#t try to enhance >> the existing filter functions instead invent a new beast leading finally to >> have the existin filter functions and your new stuff which share the same >> intention >> >> > Why don't you read previous RFC and the vote result? > https://wiki.php.net/rfc/add_validate_functions_to_filter > I'm a bit surprised by the fact there are "filter improvement" supporters. You should have participated in the previous RFC discussion. Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
