Validator's "allowEmpty" list cannot handle Objects

[someson]

Hello!

• Type: tests update
• Link to issue: allowEmpty can be populated with the list of what we consider 'empty'. The validation only will stop if the empty validation returns true. #12519

In raising this pull request, I confirm the following (please check boxes):

• I have read and understood the Contributing Guidelines?
• I have checked that another pull request for this purpose does not exist.
• I wrote some tests for this PR.

Small description of change:
Objects should be listable in Validator's allowEmpty as a possible "empty" value, i.e.

• new \Phalcon\Db\RawValue('NULL'), __toString() can be used for comparing values

As a temporary workaround I'm using currently smth. like this:

namespace Your\Namespace;

use Phalcon\Db\RawValue;
use Phalcon\Validation;
use Phalcon\Validation\Validator\Numericality as BaseNumericality;

class Numericality extends BaseNumericality
{
    public function isAllowEmpty(Validation $validation, string $fieldName): bool
    {
        $value = $validation->getValue($fieldName);
        if ($value instanceof RawValue) {
            $value = $value->getValue();
        }
        return ! $value || $value === 'NULL';
    }
}

Thanks

[niden]

Thank you!

[sergeyklay]

Why this PR has been merged?
The tests was failed: https://travis-ci.org/phalcon/cphalcon/builds/444850239

[sergeyklay]

Fixed in the #13575

[someson]

Why this PR has been merged?
The tests was failed: https://travis-ci.org/phalcon/cphalcon/builds/444850239

Because PR contains just the new test condition, that will fail without that new feature you still have to implement :)