Feature Request: Truthy Validation Rule

[dac514]

Hi,

Is it possible to create a "Truthy" validator?

That is, for my purposes, the following are all OK: true, "true", "TRUE", "True", 1, "1"

The code would look like this:

<?php
namespace Respect\Validation\Rules;

class Truthy extends AbstractRule
{
    public function validate($input)
    {
        if (is_bool($input)) {
            return $input == true;
        }

        if (is_numeric($input)) {
            return (int)$input == 1;
        }

        if (is_string($input)) {
            $input = strtolower($input);

            return $input == 'true';
        }

        return false;
    }
}

Thank you for your consideration.

[henriquemoody]

You can use v::in(array(true, 'true'))->validete(strtolower($input));, since 1 == true, '1' == true, true == true, and 'true' == 'true'.

To be honest I don't see much usage for Truthy validator, can you give us some use cases?

[alganet]

I can see the reasoning behind this. The FILTER_VALIDATE_BOOLEAN considers even "on" and "yes" as valid booleanish.

Perhaps we could provide a proxy for all FILTER_VALIDATE_ validators. That could grasp a lot of use cases.

[dac514]

Hi @henriquemoody

I'm building a REST API using SLIM. I need to validate /path/to/list?is_active=true

If I do: v::bool()->check($app->request->get('is_active', false));

I get: _error: ""true" must be a boolean",_

With /path/to/list?is_active=false

If I do your example: v::in(array(true, 'true'))->check(strtolower($app->request->get('is_active', false)));

I get: TRUE (I expect false)

And so on.

I agree with @alganet

Thank you for your consideration

[henriquemoody]

We already have yes() and no(), I'm not good with names at all, maybe we can create trueValue() and falseValue() (we already have nullValue(), were the idea came from).

Both in insensitive case:

trueValue	falseValue
1	0
true	false
'1'	'0'
'on'	'off'
'true'	'false'
'yes'	'no'

What you think?

[dac514]

I like it.

👍

[henriquemoody]

I will send a PR tomorrow! 😄

[henriquemoody]

@alganet, I've created filterVar() rule. Take a look on #267.