respect-validation/tests/unit/Rules/FalsyTest.php
Henrique Moody 562d98d805
Refactor the NotEmpty rule
Since we have the ability to use `not` as a prefix, having rules that
validate negative behaviour makes them a bit inflexible, verbose, and
harder to understand.

This commit will refactor the `NotEmpty`, and rename it to `Falsy`. It
will no longer trim strings, because Blank does a much better job at it;
it only simulates the behaviour of PHP’s native `empty()` function.

Because `Falsy`, `Blank`, and `Undef` have similar behaviour, I created
a page to demonstrate the difference and show when the user should use
one or the other.

Assisted-by: Cursor (claude-4.5-opus-high)
2025-12-29 12:48:35 +01:00

49 lines
1 KiB
PHP

<?php
/*
* Copyright (c) Alexandre Gomes Gaigalas <alganet@gmail.com>
* SPDX-License-Identifier: MIT
*/
declare(strict_types=1);
namespace Respect\Validation\Rules;
use PHPUnit\Framework\Attributes\CoversClass;
use PHPUnit\Framework\Attributes\Group;
use Respect\Validation\Test\RuleTestCase;
use stdClass;
#[Group('rule')]
#[CoversClass(Falsy::class)]
final class FalsyTest extends RuleTestCase
{
/** @return iterable<array{Falsy, mixed}> */
public static function providerForInvalidInput(): iterable
{
$rule = new Falsy();
return [
[$rule, 1],
[$rule, ' oi'],
[$rule, [5]],
[$rule, [0]],
[$rule, new stdClass()],
[$rule, ' '],
[$rule, "\n"],
];
}
/** @return iterable<array{Falsy, mixed}> */
public static function providerForValidInput(): iterable
{
$rule = new Falsy();
return [
[$rule, ''],
[$rule, false],
[$rule, null],
[$rule, []],
];
}
}