Re: Adding validate_var_array()/validate_input_array() to which version?
| From: | Yasuo Ohgaki | Date: | Thu, 04 Aug 2016 21:58:55 +0000 |
| Subject: | Re: Adding validate_var_array()/validate_input_array() to which version? | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-94841@lists.php.net to get a copy of this message | ||
Hi Rowan,
On Fri, Aug 5, 2016 at 6:47 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
>> I know naming things is hard, but I really do think "validation" is not the
>> correct name for what you are talking about. Search online for "form
>> validation", and you will see what I mean.
>>
>> The correct response to a form validation error is to show a message to the
>> user with as much detail as possible, not to simply terminate the script and
>> assume they are trying to attack your application.
>
> We are talking about different things.
> I'll document it clearly in RFC.
Different function name may help to avoid confusions.
How about
filter_assert_*()
(I'm using filter_ prefix suggested by Pierre. It's few chars longer,
but better consistency :)
These functions could be used for input mistake/error checks, but I
would like to users to use them only to assert external inputs, see if
valid(acceptable) or invalid(unacceptable) for the software.
The name may help. Hopefully.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net